Home Original page

[Python-Dev] PEP 488: elimination of PYO files

Brett Cannon brett at python.org
Sat Mar 7 23:03:18 CET 2015 
On Sat, Mar 7, 2015 at 12:39 PM Scott Dial <scott+python-dev at scottdial.com>
wrote:

> On 2015-03-06 11:34 AM, Brett Cannon wrote:
> > This PEP proposes eliminating the concept of PYO files from Python.
> > To continue the support of the separation of bytecode files based on
> > their optimization level, this PEP proposes extending the PYC file
> > name to include the optimization level in bytecode repository
> > directory (i.e., the ``__pycache__`` directory).
>
> As a packager, this PEP is a bit silent on it's expectations about what
> will happen with (for instance) Debian and Fedora packages for Python.
> My familiarity is with Fedora, and on that platform, we ship .pyc and
> .pyo files (using -O for the .pyo). Is it your expectation that such
> platforms will still distribute -O only? Or also -OO? In my world, all
> of the __pycache__ directories are owned by root.
>

I assume they will generate all .pyc files at all levels, but I don't if
it's my place to dictate such a thing since bytecode files are an
optimization to Python itself and do not influence how people interact with
the interpreter like with PEP 394 (The "python" Command on Unix-Like
Systems).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150307/b520306b/attachment.html>
More information about the Python-Dev mailing list