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 bignose
Recipients bignose, crkirkwood, docs@python, georg.brandl, r.david.murray
Date 2014-11-12.17:45:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415814355.25.0.0850788834647.issue22843@psf.upfronthosting.co.za>
In-reply-to
Content
The current wording of the passage “Match objects always have a boolean value of True” implies that the value compares equal to the ‘True’ constant. That implication is incorrect.

I disagree with R. David Murray; if we want to say that a value is considered true *in a boolean context*, that's very different from saying it has the “True” value.

Georg, “evaluates true in a boolean context” has the meaning you're seeking; it is chosen precisely because it does *not* imply equality to the True constant.
History
Date User Action Args
2014-11-12 17:45:55bignosesetrecipients: + bignose, georg.brandl, r.david.murray, docs@python, crkirkwood
2014-11-12 17:45:55bignosesetmessageid: <1415814355.25.0.0850788834647.issue22843@psf.upfronthosting.co.za>
2014-11-12 17:45:55bignoselinkissue22843 messages
2014-11-12 17:45:55bignosecreate