This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.j3
Recipients jzwinck, paul.j3
Date 2014-05-28.05:49:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401256200.43.0.251438332934.issue20430@psf.upfronthosting.co.za>
In-reply-to
Content
If we make this change to '_StoreAction', we need to do it to 4 other subclasses which take the same 'setattr(namespace, self.dest, values)'.

An alternative would be to define a 'Namespace' function that does this conditional 'setattr'.

How should this 'SUPPRESS' affect the usage and help?  I'm seeing "--foo ==SUPPRESS==".

Do you have practical need for such a 'SUPPRESS', or are you just trying to make behavior consistent?  'SUPPRESS' is used for '--help' and subparsers because those Actions have important side effects, and we don't want default values to appear in the Namespace.  With '_StoreAction', the only effect is to store a value in the Namespace.
History
Date User Action Args
2014-05-28 05:50:00paul.j3setrecipients: + paul.j3, jzwinck
2014-05-28 05:50:00paul.j3setmessageid: <1401256200.43.0.251438332934.issue20430@psf.upfronthosting.co.za>
2014-05-28 05:50:00paul.j3linkissue20430 messages
2014-05-28 05:49:59paul.j3create