Message145733
| 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 |
<CACac1F8Wp5S-wq=cMrOwj0tvSfifk9Q6=-iDxqJkxYbWfR=3YA@mail.gmail.com> |
| In-reply-to |
<1318857980.75.0.521925834297.issue13172@psf.upfronthosting.co.za> |
| Content |
> 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. |
|