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 Julien Baley, docs@python, paul.j3, r.david.murray
Date 2015-10-06.20:16:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444162583.26.0.352775518515.issue25314@psf.upfronthosting.co.za>
In-reply-to
Content
I have seen questions on StackOverflow with 'store_true' and explicit `default=False` parameters.  I don't recall any where this was a problem.  Usually it's as harmless as users specifying other defaults like `action='store'`, or a dest that echos a long option, etc.

But if we are going to fix the wrong default statement in `store_const`, we might as well clarify this case as well.

I wonder if this is the time and place to add a note that specifying 'type' is not necessary (and even wrong) - re. this closed issue: http://bugs.python.org/issue24754 

Is the line  'These are special cases of ``'store_const'``' useful?   The statement echos the class definition

    class _StoreTrueAction(_StoreConstAction)

but I'm not sure it adds much to the user's understanding.  'store_true' and 'store_false' are used frequently; 'store_const' is much less common (based on SO questions).
History
Date User Action Args
2015-10-06 20:16:23paul.j3setrecipients: + paul.j3, r.david.murray, docs@python, Julien Baley
2015-10-06 20:16:23paul.j3setmessageid: <1444162583.26.0.352775518515.issue25314@psf.upfronthosting.co.za>
2015-10-06 20:16:23paul.j3linkissue25314 messages
2015-10-06 20:16:22paul.j3create