Message172364
| Author |
neologix |
| Recipients |
Arfrever, brett.cannon, eric.snow, neologix, pitrou, rpetrov, sbt, vstinner |
| Date |
2012年10月08日.07:51:58 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAH_1eM2w+cFC2TySXVghJ0jR92pp5oDBb7Aff_y5n0j=dhV7zA@mail.gmail.com> |
| In-reply-to |
<1349606859.53.0.699931115322.issue15833@psf.upfronthosting.co.za> |
| Content |
> Yes .
> Charles, lest assume that all other issues with build system, are resolved and source tree is ready for use. So in this situation I could run python , I could build all and I could run tests with an additional patch TEMPDIR is relative to build tree (patch 0014-* from recent archive uploaded to issue #3754) . Note without you patch.
>
> In my build environment test_imp fail on test_source.
> So what is result with you patch on this test ?
Sorry, I'm not a native English speaker, and I don't understand what
you're talking about.
The issue at hand is that bytecode creation only catches EPERM and
EEXIST, but other errors can be raised on a read-only filesystem
(EROFS, EIO in some strange cases). |
|