Sense this is something new, I believe it is helpful to look at all the
possibilities so it doesn't become something we regret we did later. This
is something that once it gets put in place may be real hard to get rid of.
So here are a few questions that I think haven't seen asked yet.
What command line options will be available to alter how python uses .pyo,
pyc., and pyr located files?
What's the easiest way to remove all pyr dirs and files?
What's the easiest way to remove pyr dirs files for one project?
Would having python command line argument(s) to remove bytecode make sense?
Would it be possible to have one single python system __pycache__ directory
and put all bytecode in it?
Instead of subdirectories in the pyr or __cache__ directory, would it be
possible to just use unique names and not have multiple sub directories.
# some place on the users disk
someplace/
foobar/
__init__.py
foo.py
foobar2/
bar.py
# someplace on the system disk
___pycache__/
v027.xyz.foobar.__init__.py
v027.xyz.foobar.foo.pyc
v030.xyz.foobar.__init__.py
v030.xyz.foobar.foobar2.bar.pyc
# where 'xyz' identifies a unique location to differentiate when there is
more than one copy of a program. (They may not be exactly the same, but my
have the same file names.)
# I like the version id up front because it doesn't intermix different
version files together.
With a single cache directory, we could have an option to force writing
bytecode to a desired location. That might be useful on it's own for
creating runtime bytecode only installations for installers.
Ron
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
