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 veky
Recipients brandtbucher, iritkatriel, veky
Date 2022-01-02.14:46:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641134787.69.0.478458531487.issue46219@roundup.psfhosted.org>
In-reply-to
Content
A long time ago, Python documentation used true and false as adjectives (as opposed to True and False, which are proper names for canonical true/false objects). I think it was BDFL's preference back then.

In the meantime, I suppose through JS's influence, Python documentation started to adopt ancient Perl terminology, where truhy and falsy were used as adjectives standing for what was previously known as true and false. I really don't like it, and I think English language is clear enough here (given the help of code font and capital letter) that we don't need to invent new words. Of course, it is up to the community to decide (and maybe the steering council might issue an opinion), but I'm telling you the history and my preference.
History
Date User Action Args
2022-01-02 14:46:28vekysetrecipients: + veky, brandtbucher, iritkatriel
2022-01-02 14:46:27vekysetmessageid: <1641134787.69.0.478458531487.issue46219@roundup.psfhosted.org>
2022-01-02 14:46:27vekylinkissue46219 messages
2022-01-02 14:46:27vekycreate