[Python-Dev] __file__ and bytecode-only
fuzzyman at voidspace.org.uk
Fri Mar 12 23:48:42 CET 2010
On 12/03/2010 19:53, Barry Warsaw wrote:
> On Mar 04, 2010, at 11:34 PM, Nick Coghlan wrote:
>> The remaining open question to my mind is whether or not there should be
>> a -X option to control the bytecode generation. E.g.:
>> -Xcache_bytecode=no (don't write bytecode files at all)
> -B and $PYTHONDONTWRITEBYTECODE will still be supported and serve this use
>> -Xcache_bytecode=file (write a classic "foo.pyc" file)
>> -Xcache_bytecode=dir (write to the "__pycache__" directory)
>> With cache_bytecode=dir being the default for future releases.
> I believe we've decided /not/ to support creation of bytecode-only
> distributions out of the box.
I thought Guido said on this topic :
" FWIW, I started at -1 and am still -1. I think the PEP is overreaching
in this aspect; it does not serve the stated purpose of the PEP to
make life easier for distros that share code between Python versions."
Has something changed since then?
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev