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 paul.moore
Recipients alexis, eric.araujo, paul.moore, tarek, vinay.sajip
Date 2011-10-17.17:18:58
SpamBayes Score 2.02877e-05
Marked as misclassified No
Message-id <>
In-reply-to <>
> Would you be satisfied with a more helpful traceback that would point you immediately to missing msi?  Do you prefer that bdist_msi
> catch an ImportError for _msi and print a short error message instead of a traceback in all its glory?

I'd be happy with a more explicit error. As you say, it's a broken
build so not worth worrying too much about, but it did take me quite a
while to work out what the problem was, including having to raise this
bug report. (The existing traceback doesn't even mention _msi).

So yes, a simple error would be ideal.
Date User Action Args
2011-10-17 17:18:59paul.mooresetrecipients: + paul.moore, vinay.sajip, tarek, eric.araujo, alexis
2011-10-17 17:18:58paul.moorelinkissue13172 messages
2011-10-17 17:18:58paul.moorecreate