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 BrenBarn
Recipients BrenBarn, Radu.Ciorba, berker.peksag, bethard, chris.jerdonek, hashimo, nanjekyejoannah, paul.j3, r.david.murray, rhettinger, sebix, terry.reedy
Date 2019-08-19.00:49:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566175787.4.0.432878502654.issue16468@roundup.psfhosted.org>
In-reply-to
Content
Here is an example of someone who cares about the behavior and/or the documentation (and still cares enough to check up on their StackOverflow question six years later): https://stackoverflow.com/questions/13833566/python-argparse-choices-from-an-infinite-set/13833736 .

The issue is not the use of the word "container".  The docs literally say "Any object that supports the `in` operator can be passed as the choices value" and that is not true.  In fact, changing it to say "any container type" would be an improvement as that is at least arguably correct, whereas the current documentation is unambiguously incorrect.
History
Date User Action Args
2019-08-19 00:49:47BrenBarnsetrecipients: + BrenBarn, rhettinger, terry.reedy, bethard, r.david.murray, chris.jerdonek, berker.peksag, paul.j3, hashimo, Radu.Ciorba, sebix, nanjekyejoannah
2019-08-19 00:49:47BrenBarnsetmessageid: <1566175787.4.0.432878502654.issue16468@roundup.psfhosted.org>
2019-08-19 00:49:47BrenBarnlinkissue16468 messages
2019-08-19 00:49:47BrenBarncreate