Message265259
> 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. |
|
Date |
User |
Action |
Args |
2016-05-10 18:55:22 | Nathan Naze | set | recipients:
+ Nathan Naze, r.david.murray |
2016-05-10 18:55:22 | Nathan Naze | set | messageid: <1462906522.76.0.10265284981.issue26994@psf.upfronthosting.co.za> |
2016-05-10 18:55:22 | Nathan Naze | link | issue26994 messages |
2016-05-10 18:55:22 | Nathan Naze | create | |
|