New submission from Nathan Naze:
Setting a boolean type in argparse gives unexpected behavior when setting
"True", "False", etc.
https://gist.github.com/nanaze/db63e3f63e318408e3223bf1245d9752
Would have expected parsing to fail for unclear input that doesn't neatl
Nathan Naze added the comment:
> It does 'bool(value)', and 'bool("False")' is True, since "False" is a
> non-empty string.
Yes, I understand this. It's fine to mark as "working as intended", but coming
from other flag-parsing libr
Nathan Naze added the comment:
I also buy the argument that changing the behavior now would be problematic
given the existing usages in the wild.
--
___
Python tracker
<http://bugs.python.org/issue26
