This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author unfamiliarplace
Recipients docs@python, josh.r, unfamiliarplace
Date 2016-04-26.04:22:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461644522.81.0.575078374949.issue26847@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-04-26 04:22:02unfamiliarplacesetrecipients: + unfamiliarplace, docs@python, josh.r
2016-04-26 04:22:02unfamiliarplacesetmessageid: <1461644522.81.0.575078374949.issue26847@psf.upfronthosting.co.za>
2016-04-26 04:22:02unfamiliarplacelinkissue26847 messages
2016-04-26 04:22:02unfamiliarplacecreate