[Python-Dev] __pycache__ creation

Barry Warsaw barry at python.org
Tue Mar 23 23:37:16 CET 2010

On Mar 22, 2010, at 09:47 PM, Martin v. Löwis wrote:

>Therefore, I'm in favor of having it on by default. If certain use cases
>make it problematic (e.g. Apache creating directories which you then
>cannot delete), there should be a way to turn it *off*. Perhaps the
>existing machinery to turn of byte code generation at all might be

That's what I'm thinking.  Of course it will always be possible to run
compileall and get the __pycache__ directories pre-created, presumably with
the right umask.

>As for the original question (funny umasks), I think my proposal is
>"tough luck". Don't try to be super-smart; as Antoine explains, it gets
>worse, not better. If the user has arranged that Python will create
>unusable directories, the user better changes his setup.

I completely agree; +1

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100323/38d3f9c5/attachment.pgp>

More information about the Python-Dev mailing list