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 Claudiu.Popa
Recipients Claudiu.Popa, eric.smith, eric.snow, ezio.melotti, michael.foord
Date 2013-11-22.21:38:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Added patch which addresses Eric's comments. It contains a situation which I'm not so happy, mostly due to not knowing in depth (or at least at a comfortable level) the import mechanics: in the AttributeError except handler, if the spec can't be determined and the module is not built-in, a TypeError is raised to notice the user that discovery can't be done for that particular package. Probably this situation (no __file__, no __spec__ and no built-in) is common, but I can't think right now at another way of solving it.
Date User Action Args
2013-11-22 21:38:32Claudiu.Popasetrecipients: + Claudiu.Popa, eric.smith, ezio.melotti, michael.foord, eric.snow
2013-11-22 21:38:32Claudiu.Popasetmessageid: <>
2013-11-22 21:38:32Claudiu.Popalinkissue17457 messages
2013-11-22 21:38:32Claudiu.Popacreate