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 brett.cannon
Recipients Arfrever, Marc.Abramowitz, Ronan.Lamy, brett.cannon, eric.snow, jcea, ncoghlan
Date 2012-11-16.19:08:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353092884.59.0.358881695541.issue15031@psf.upfronthosting.co.za>
In-reply-to
Content
In order to have exceptions that have messages like "bad magic number in module" there would need to be a technically unneeded fullname parameter. People cool with that? I personally dislike having info passed in just for error reporting, but in this case import exceptions typically try to clarify what actually caused the issue by naming the module since you can end up with deep implicit module chains.

The other stuff related to bytecode paths are just for verbose logging or for setting path on ImportError, both of which can be worked around.
History
Date User Action Args
2012-11-16 19:08:04brett.cannonsetrecipients: + brett.cannon, jcea, ncoghlan, Arfrever, eric.snow, Marc.Abramowitz, Ronan.Lamy
2012-11-16 19:08:04brett.cannonsetmessageid: <1353092884.59.0.358881695541.issue15031@psf.upfronthosting.co.za>
2012-11-16 19:08:04brett.cannonlinkissue15031 messages
2012-11-16 19:08:04brett.cannoncreate