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 r.david.murray
Recipients alexgarel, chris.jerdonek, michael.foord, r.david.murray, rbcollins, slmnhq
Date 2012-06-01.19:48:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I updated the tests to Python3, and attempted to replicate the fix using the new importlib qualname support.  Even if it had worked, this would not have finished the patch, since Michael wants to generate a failing test instead of raising the import error.

However, I'm running into weird problems and am shelving this for the moment.  The issue is that if I run the tests like this:

   ./python -m unittest test.test_unittest

(or via regrtest) they fail with the wrong name in the error message.  If I run them like this:

    ./python -m unittest unittest.test.test_loader.TestLoader.<name of test>

the right name is in the message.  I suspect the bug is in the tests, but I'm not spotting it.  Maybe someone else will see it.
Date User Action Args
2012-06-01 19:48:03r.david.murraysetrecipients: + r.david.murray, rbcollins, michael.foord, slmnhq, chris.jerdonek, alexgarel
2012-06-01 19:48:02r.david.murraysetmessageid: <>
2012-06-01 19:48:01r.david.murraylinkissue7559 messages
2012-06-01 19:48:00r.david.murraycreate