Message138485
| Author |
vinay.sajip |
| Recipients |
Arfrever, barry, eric.araujo, ned.deily, r.david.murray, vinay.sajip |
| Date |
2011年06月17日.00:56:58 |
| SpamBayes Score |
2.6067204e-11 |
| Marked as misclassified |
No |
| Message-id |
<413625.10232.qm@web25806.mail.ukl.yahoo.com> |
| In-reply-to |
<1308270667.9.0.783025710979.issue12313@psf.upfronthosting.co.za> |
| Content |
> OK, now I'm really confused. I tried to reproduce this by installing from my
>checkout into a work dir, and then running regrtest using that installed
>python, and discovered that test_email and its data directory got copied by the
>installation process. (There were test failures, so I'll have to work on
>that...) This is without any mention of test_email in the Makefile I used to
>do the 'make install'.
That does seem odd. On my pythonv fork (which follows the cpython repo pretty
closely), the only current failures are test_lib2to3, test_packaging and
test_sysconfig - all of which failures are already the subject of tickets on the
tracker. On my system at least, test_email doesn't show up any failures. See the
latest version of the test log from the Gist link I posted earlier - the comment
also references the failure tickets. |
|