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 gregory.p.smith
Recipients gregory.p.smith, ncoghlan, rhettinger, serhiy.storchaka
Date 2021-05-02.02:06:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1619921172.75.0.358046767675.issue44003@roundup.psfhosted.org>
In-reply-to
Content
Oh, I didn't realize mutating those would actually change the code runtime behavior.  But it makes sense, those are needed before the code object is entered.

Yeah that is different, and suggests making this the default is not actually desired.  (this issue and the other one)

I guess our rule is that introspection code really must check for and be ready to handle .__wrapped__ if its goal is robustness?
History
Date User Action Args
2021-05-02 02:06:12gregory.p.smithsetrecipients: + gregory.p.smith, rhettinger, ncoghlan, serhiy.storchaka
2021-05-02 02:06:12gregory.p.smithsetmessageid: <1619921172.75.0.358046767675.issue44003@roundup.psfhosted.org>
2021-05-02 02:06:12gregory.p.smithlinkissue44003 messages
2021-05-02 02:06:12gregory.p.smithcreate