PEP 304 - is anyone really interested?
I wrote PEP 304, "Controlling Generation of Bytecode Files": http://www.python.org/peps/pep-0304.html quite awhile ago. The first version appeared in January 2003 in response to questions from people about controlling/suppressing bytecode generation in certain situations. It sat idle for a long while, though from time-to-time people would ask about the functionality and I'd respond or update the PEP. In response to another recent question about this topic: http://mail.python.org/pipermail/python-list/2005-June/284775.html and a wave of recommendations by Raymond Hettinger regarding several other PEPs, I updated the patch to work with current CVS. Aside from one response by Thomas Heller noting that my patch upload failed (and which has been corrected since), I've seen no response either on python-dev or comp.lang.python. I really have no personal use for this functionality. I control all the computers on which I use Python and don't use any exotic hardware (which includes Windows as far with its multi-rooted file system as far as I'm concerned), don't run from read-only media or think that in-memory file systems are much of an advantage over OS caching. The best I will ever do with it is respond to people's inputs. I'd hate to see it sit for another two years. If someone out there is interested in this functionality and would benefit more from its incorporation into the core, I'd be happy to hand it off to you. So speak up folks, otherwise my recommendation is that it be put out of its misery. Skip
[Skip Montanaro wrote]
I wrote PEP 304, "Controlling Generation of Bytecode Files":
http://www.python.org/peps/pep-0304.html
... So speak up folks, otherwise my recommendation is that it be put out of its misery.
I've had use for it before, but have managed to work around the problems. I think it is a good feature, but I wouldn't have the time to shepherd the patch. Trent -- Trent Mick TrentM@ActiveState.com
Skip Montanaro wrote:
I wrote PEP 304, "Controlling Generation of Bytecode Files":
I would like to see some way of having bytecode files put into platform/version dependent subdirectories, which would make it easier e.g. to have Python code shared over a network between machines of different architectures or running different Python versions. But the scheme this PEP proposes (a single session-wide location) is too coarse-grained for what I have in mind. So I would not support this particular PEP without sufficiently large changes that it might as well become a new PEP. -- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg.ewing@canterbury.ac.nz +--------------------------------------+
On Jun 23, 2005, at 10:11 PM, Greg Ewing wrote:
Skip Montanaro wrote:
I wrote PEP 304, "Controlling Generation of Bytecode Files":
I would like to see some way of having bytecode files put into platform/version dependent subdirectories, which would make it easier e.g. to have Python code shared over a network between machines of different architectures or running different Python versions. But the scheme this PEP proposes (a single session-wide location) is too coarse-grained for what I have in mind. So I would not support this particular PEP without sufficiently large changes that it might as well become a new PEP.
You could implement that in your sitecustomize.py, unless you have Python interpreters that change platform or version mid-session. I don't see why it needs to be subdirectories, you could make the bytecode cache local or somewhere on the server that you have write access to. -bob
participants (4)
-
Bob Ippolito -
Greg Ewing -
Skip Montanaro -
Trent Mick