Message115502
| Author |
Steve.Thompson |
| Recipients |
Steve.Thompson, amaury.forgeotdarc, barry, brian.curtin, markon, mucisland, pdsimanyi, pitrou |
| Date |
2010年09月03日.20:38:48 |
| SpamBayes Score |
3.6349416e-08 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTimi0Ofxq0CgJyxUmrFBTdZwbdD93SA36AA1fa7t@mail.gmail.com> |
| In-reply-to |
<1283546190.96.0.389810289369.issue6074@psf.upfronthosting.co.za> |
| Content |
Any idea if this will be fixed (at all) and/or back ported to 2.6.x or
2.7.x?
On Fri, Sep 3, 2010 at 3:36 PM, Amaury Forgeot d'Arc <report@bugs.python.org
> wrote:
>
> Amaury Forgeot d'Arc <amauryfa@gmail.com> added the comment:
>
> This is still the case: on Windows, if foo.py is readonly,
> python -c "import foo"
> generates foo.pyc with the readonly attribute.
>
> Tested with 3.1 and current py3k (where the file is named
> __pycache__\foo.cpython-32.pyc)
>
> ----------
> nosy: +amaury.forgeotdarc
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue6074>
> _______________________________________
> |
| Files |
|---|
| File name |
Uploaded |
|
unnamed
|
Steve.Thompson,
2010年09月03日.20:38:48
|
|