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 xtreak
Recipients Amir, Darragh Bailey, anthonypjshaw, aviso, cjw296, lisroach, mariocj89, michael.foord, pconnell, r.david.murray, rbcollins, serhiy.storchaka, xtreak
Date 2020-04-22.12:54:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The patch assumed using the magic method attribute as the way to evaluate an object in a context which I got to know is wrong since evaluations in context like boolean are not only dependent on one magic method but has a precedence over several others. In the event of 3.9 alpha 6 being the next candidate I guess the change can be reverted to be revisited later about the desired behaviour with backwards compatibility. The docs could perhaps be clarified that calling magic method on a wrap gives default set of values. 

Thoughts on reversion or other possible approaches?
Date User Action Args
2020-04-22 12:54:30xtreaksetrecipients: + xtreak, rbcollins, cjw296, r.david.murray, michael.foord, serhiy.storchaka, pconnell, Darragh Bailey, lisroach, anthonypjshaw, mariocj89, aviso, Amir
2020-04-22 12:54:30xtreaksetmessageid: <>
2020-04-22 12:54:30xtreaklinkissue39966 messages
2020-04-22 12:54:29xtreakcreate