Brendan Barnwell added the comment:
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
Brendan Barnwell added the comment:
This issue has sat idle for six years. Meanwhile, the docs are still
incorrect, giving every user wrong information about how the module works. Can
we consider just changing the documentation instead of worrying about what the
behavior should be or what
Brendan Barnwell added the comment:
This issue has sat idle for six years. Meanwhile, the docs are still
incorrect, giving every user wrong information about how the module works. Can
we consider just changing the documentation instead of worrying about what the
behavior should be or what
Brendan Barnwell added the comment:
https://bugs.python.org/issue16468
--
nosy: +BrenBarn
versions: +Python 3.7
___
Python tracker
<https://bugs.python.org/issue16
Brendan Barnwell added the comment:
This needs to be fixed. The documentation for the behavior of += on lists
needs to be with the documentation on lists. The existing, vague documentation
that += works in-place "when possible" is insufficient.
A central feature
New submission from Brendan Barnwell:
With the fix of issue #17903 in place, the behavior of the Windows launcher for
a shebang of #!/usr/bin/env python is now different from the behavior for the
other virtual commands in that the PATH is searched for this particular
virtual command
