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 michael.foord
Recipients michael.foord, r.david.murray, rbcollins, slmnhq
Date 2010-01-09.17:08:32
SpamBayes Score 1.95483e-06
Marked as misclassified No
Message-id <>
I'm unhappy with a straight change in behaviour because it will break code that is currently catching AttributeError.

A slightly less invasive change would be to raise an AttributeError if the module doesn't exist, otherwise letting the original error propagate.

That means distinguishing between a module not existing and an ImportError raised whilst importing the module. Example code that does this by walking the stack:

In addition we could add a new method that loads a test from name, returning an 'ErrorHolder' if loading the test fails. (A TestCase that reraises the original error when run - test discovery already does this in fact so that a test module failing to load doesn't halt discovery.)
Date User Action Args
2010-01-09 17:08:36michael.foordsetrecipients: + michael.foord, rbcollins, r.david.murray, slmnhq
2010-01-09 17:08:35michael.foordsetmessageid: <>
2010-01-09 17:08:33michael.foordlinkissue7559 messages
2010-01-09 17:08:33michael.foordcreate