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 libraries, I find the behavior unintuitive and do not
understand the utility of accepting arbitrary strings given the potential for
user confusion. We uncovered this behavior debugging a script used internally
at Google.
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue26994>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
