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, xtreak
Date 2020-03-28.04:00:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> What may make more sense for some magic methods is to call the underlying object and use the return value or raise any exception that occurs.

Sorry, isn't that what the previous issue did? It tries to return the wrapped object attribute and raises exception if attribute is not present. Using wrapped object attribute and falling back to default value means that it will always return a value but the user can't figure out if it's from wrapped object or the default value for the magic method.
Date User Action Args
2020-03-28 04:00:02xtreaksetrecipients: + xtreak, rbcollins, cjw296, r.david.murray, michael.foord, pconnell, Darragh Bailey, lisroach, anthonypjshaw, mariocj89, aviso, Amir
2020-03-28 04:00:02xtreaksetmessageid: <>
2020-03-28 04:00:02xtreaklinkissue39966 messages
2020-03-28 04:00:02xtreakcreate