➜

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 terry.reedy
Recipients Jeremy.Hylton, Ramchandra Apte, cool-RR, eric.araujo, ezio.melotti, ncoghlan, pjenvey, terry.reedy
Date 2013-02-20.05:08:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361336936.74.0.896434742429.issue17032@psf.upfronthosting.co.za>
In-reply-to
Content 
+    NAME_ERROR_MSGy, name);
will give a NameError ;-).

The patch undoes the change from 'name' to 'global name'. Skimming the PEP, I do not see this change mandated or justified by the PEP. So my current view: while it is true that it is the final, global name lookup that fails, I agree with Ram that it is not necessarily a global name that was mistyped or is missing. So in absence of better justification of the status quo, I would apply the patch. Backport to 3.3 would be ok but not necessary, as the message is not nearly as wrong as some have been.
History
Date User Action Args
2013-02-20 05:08:56terry.reedysetrecipients: + terry.reedy, ncoghlan, pjenvey, ezio.melotti, eric.araujo, cool-RR, Jeremy.Hylton, Ramchandra Apte
2013-02-20 05:08:56terry.reedysetmessageid: <1361336936.74.0.896434742429.issue17032@psf.upfronthosting.co.za>
2013-02-20 05:08:56terry.reedylinkissue17032 messages
2013-02-20 05:08:56terry.reedycreate