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 arigo
Recipients arigo, larry
Date 2015-06-23.17:40:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A regression in 3.5: if we use custom objects as modules (like some projects do), then these custom objects may not have an attribute called "__name__".  There is new code in 3.5 added for issue #17636 which tries sometimes to read the "__name__" of a module when executing an import statement, and if this leads to an AttributeError, it will get propagated.

I imagine this could break real code using "try: except ImportError:".  It _does_ break the tests of the "cffi" project, which try to check that some import of a nonexisting name correctly gives ImportError.  Now it gives AttributeError("__name__") instead.
Date User Action Args
2015-06-23 17:40:13arigosetrecipients: + arigo, larry
2015-06-23 17:40:13arigosetmessageid: <>
2015-06-23 17:40:13arigolinkissue24492 messages
2015-06-23 17:40:13arigocreate