<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 12/03/2010 19:53, Barry Warsaw wrote:
<blockquote cite="mid:20100312145312.1f0a0aa0@heresy.wooz.org"
type="cite">
<pre wrap="">On Mar 04, 2010, at 11:34 PM, Nick Coghlan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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)
</pre>
</blockquote>
<pre wrap="">
-B and $PYTHONDONTWRITEBYTECODE will still be supported and serve this use
case.
</pre>
<blockquote type="cite">
<pre wrap="">-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.
</pre>
</blockquote>
<pre wrap="">
I believe we've decided /not/ to support creation of bytecode-only
distributions out of the box.
</pre>
</blockquote>
<br>
I thought Guido said on this topic [1]:<br>
<br>
"
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
FWIW, I started at -1 and am still -1. I think the PEP is overreaching<br>
in this aspect; it does not serve the stated purpose of the PEP to<br>
make life easier for distros that share code between Python versions."<br>
<br>
Has something changed since then?<br>
<br>
Michael<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://mail.python.org/pipermail/python-dev/2010-March/098098.html">http://mail.python.org/pipermail/python-dev/2010-March/098098.html</a><br>
<blockquote cite="mid:20100312145312.1f0a0aa0@heresy.wooz.org"
type="cite">
<pre wrap="">
-Barry
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Python-Dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Python-Dev@python.org">Python-Dev@python.org</a>
<a class="moz-txt-link-freetext" href="http://mail.python.org/mailman/listinfo/python-dev">http://mail.python.org/mailman/listinfo/python-dev</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk">http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.ironpythoninaction.com/">http://www.ironpythoninaction.com/</a>
<a class="moz-txt-link-freetext" href="http://www.voidspace.org.uk/blog">http://www.voidspace.org.uk/blog</a>
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.
</pre>
</body>
</html>