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 | sbt |
|---|---|
| Recipients | brett.cannon, sbt |
| Date | 2012年08月31日.16:57:25 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1346432246.49.0.876284426658.issue15833@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
As discussed in http://bugs.python.org/issue15819 trying to run python built outside a read-only source directory fails for me because OSError(EIO, ...) is raised when importlib tries to write the byte compiled file. (I built python in a Linux VM using VMware Player which only had read-only access to the source directory.) Currently importlib only ignores PermissionError (EACCES, EPERM) and FileExistsError (EEXIST): http://hg.python.org/cpython/file/d54f047312a8/Lib/importlib/_bootstrap.py#l1080 Under Python 3.2 all failures are ignored: http://hg.python.org/cpython/file/69952b5599b5/Python/import.c#l905 so this seems to be a regression. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年08月31日 16:57:26 | sbt | set | recipients: + sbt, brett.cannon |
| 2012年08月31日 16:57:26 | sbt | set | messageid: <1346432246.49.0.876284426658.issue15833@psf.upfronthosting.co.za> |
| 2012年08月31日 16:57:25 | sbt | link | issue15833 messages |
| 2012年08月31日 16:57:25 | sbt | create | |