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 nascheme
Recipients eric.smith, nascheme, steven.daprano, thautwarm, vtheno athena
Date 2018-10-03.16:10:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538583043.11.0.545547206417.issue34880@psf.upfronthosting.co.za>
In-reply-to
Content
Assuming it is not crazy complicated to fix, I would like to to be changed.  It should work like the TypeError example.  That fact that it has worked the current way since Python 1.5 isn't a strong argument.  I think no one should be surprised if it changes.  Also, expecting other Python implementations to match the LOAD_GLOBAL behavior seems to put unnecessary burden on them.  If someone writes code that relies on that behavior, they should not be surprised if it gets broken, IMHO.
History
Date User Action Args
2018-10-03 16:10:43naschemesetrecipients: + nascheme, eric.smith, steven.daprano, thautwarm, vtheno athena
2018-10-03 16:10:43naschemesetmessageid: <1538583043.11.0.545547206417.issue34880@psf.upfronthosting.co.za>
2018-10-03 16:10:43naschemelinkissue34880 messages
2018-10-03 16:10:43naschemecreate