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 brian.curtin
Recipients amaury.forgeotdarc, brian.curtin, cgohlke, georg.brandl, loewis, ncoghlan, techtonik
Date 2011-07-27.04:01:52
SpamBayes Score 2.08361e-05
Marked as misclassified No
Message-id <>
How about something like this?

ImportError moves from being a "simple" exception to a "complex" one, then adds a "name" and "path" attribute. In dynload_win.c where we try (and fail) to load C extensions, the name and path are set on the ImportError. The test simply creates a file following the C extension name format and checks that the attributes end up being correct upon ImportError.

Jazzing up the ImportErrors elsewhere in the code might be useful after this, but I'll handle that in another issue if this gains traction.
Date User Action Args
2011-07-27 04:01:53brian.curtinsetrecipients: + brian.curtin, loewis, georg.brandl, amaury.forgeotdarc, ncoghlan, techtonik, cgohlke
2011-07-27 04:01:53brian.curtinsetmessageid: <>
2011-07-27 04:01:52brian.curtinlinkissue10854 messages
2011-07-27 04:01:52brian.curtincreate