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 pitrou
Recipients emptysquare, eric.snow, grahamd, ncoghlan, pitrou
Date 2015-07-03.10:41:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435920078.51.0.140045861865.issue24554@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think this is a very important issue, by the way. Normal destructors will usually rely on resources on their global environment, i.e. the function's globals or builtins dict, which will point to the right namespace. Only if you are explicitly looking up something on the interpreter (or using e.g. thread-local storage... but relying on thread-local storage in a destructor is already broken anyway) will you see such discrepancies.
History
Date User Action Args
2015-07-03 10:41:18pitrousetrecipients: + pitrou, ncoghlan, grahamd, eric.snow, emptysquare
2015-07-03 10:41:18pitrousetmessageid: <1435920078.51.0.140045861865.issue24554@psf.upfronthosting.co.za>
2015-07-03 10:41:18pitroulinkissue24554 messages
2015-07-03 10:41:18pitroucreate