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 amaury.forgeotdarc
Recipients amaury.forgeotdarc
Date 2012-06-20.00:17:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340151446.59.0.121813331775.issue15111@psf.upfronthosting.co.za>
In-reply-to
Content
Up to Python3.2, a nested ImportError was correctly displayed:

./python -c "import distutils.msvc9compiler"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/amauryfa/python/cpython3.2/Lib/distutils/msvc9compiler.py", line 27, in <module>
    import winreg
ImportError: No module named winreg

But with 3.3, the traceback is lost:

~/python/cpython3.x$ ./python -c "from distutils import msvc9compiler"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: cannot import name msvc9compiler

Even though the failure is still on the "import winreg" line. Only ImportError seems affected, other exceptions are correctly displayed.
History
Date User Action Args
2012-06-20 00:17:27amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc
2012-06-20 00:17:26amaury.forgeotdarcsetmessageid: <1340151446.59.0.121813331775.issue15111@psf.upfronthosting.co.za>
2012-06-20 00:17:25amaury.forgeotdarclinkissue15111 messages
2012-06-20 00:17:21amaury.forgeotdarccreate