Message264209
josh, we're saying the same thing but misunderstanding each other. :)
I realize that they can be empty containers, etc., and that's why I think "equal to False" is appropriate -- because those things *are* equal to False:
>>> [] == False
True
>>> 0 == False
True
etc.
However, they are not identical to False:
>>> [] is False
False
>>> 0 is False
False
And that's why I think the wording "are false" is potentially misleading.
Perhaps there's a better wording than "equal to False" (compares equivalently to False? or simply: are falsey? :p), but anyhow, we're identifying the same behaviour here. |
|
Date |
User |
Action |
Args |
2016-04-26 04:22:02 | unfamiliarplace | set | recipients:
+ unfamiliarplace, docs@python, josh.r |
2016-04-26 04:22:02 | unfamiliarplace | set | messageid: <1461644522.81.0.575078374949.issue26847@psf.upfronthosting.co.za> |
2016-04-26 04:22:02 | unfamiliarplace | link | issue26847 messages |
2016-04-26 04:22:02 | unfamiliarplace | create | |
|