[Python-Dev] PEP 3147, pycache directories and umask (original) (raw)
Barry Warsaw barry at python.org
Wed Mar 24 00:07:24 CET 2010
- Previous message: [Python-Dev] PEP 3147, __pycache__ directories and umask
- Next message: [Python-Dev] PEP 3147, __pycache__ directories and umask
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mar 23, 2010, at 12:49 PM, Russell E. Owen wrote:
If .pyc files are to be shared, it seems essential to (by default) generate them at install time and make them read-only for unprivileged users.
I think in practice this is what's almost always going to happen for system Python source, either via your distribution's installer or distutils. I think most on-demand creation of pyc files will be when you're developing your own code. I don't want to have to run a separate step to get the benefit of pycache, but I admit it's outside the scope of the PEP's original intention. I leave it to the BDFL.
-Barry -------------- 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/fc7697e0/attachment.pgp>
- Previous message: [Python-Dev] PEP 3147, __pycache__ directories and umask
- Next message: [Python-Dev] PEP 3147, __pycache__ directories and umask
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]