Author pde
Recipients pde
Date 2016-11-19.00:23:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479515002.77.0.106617247567.issue28742@psf.upfronthosting.co.za>
In-reply-to
Content
One thing I noticed when testing my patch by vendorizing it into the Certbot tree was that if a developer had somehow inherited from a version of argparse.Action that *doesn't* have this patch applied to it, and then passes in instances of those inheriting classes to the new patched version, things will break (because the argparse engine now assumes every action has a help_default attribute, rather than checking for it).

That's an unlikely situation but might arise if a developer had managed to use the standard library version of argparse in some places, and the pypi packaged version in other places.

It might be possible, but uglier, to write this patch more defensively so that that wouldn't happen; I would appreciate some feedback on whether people think that's necessary or a good idea.
History
Date User Action Args
2016-11-19 00:23:22pdesetrecipients: + pde
2016-11-19 00:23:22pdesetmessageid: <1479515002.77.0.106617247567.issue28742@psf.upfronthosting.co.za>
2016-11-19 00:23:22pdelinkissue28742 messages
2016-11-19 00:23:22pdecreate