mirror of
https://github.com/python/cpython.git
synced 2025-09-26 10:19:53 +00:00
rephrase
This commit is contained in:
parent
55871f04bf
commit
e328323cf7
1 changed files with 7 additions and 7 deletions
|
@ -253,13 +253,13 @@ PEP 488: Elimination of PYO files
|
|||
---------------------------------
|
||||
|
||||
:pep:`488` does away with the concept of ``.pyo`` files. This means that
|
||||
``.pyc`` files represent both unoptimized and optimized bytecode. To prevent
|
||||
the need to constantly regenerate bytecode files, ``.pyc`` files now have an
|
||||
optional ``opt-`` tag in their name when the bytecode is optimized. This has
|
||||
the side-effect of no more bytecode file name clashes when running under either
|
||||
``-O`` or ``-OO``, thus allowing unoptimized, ``-O``, and ``-OO`` bytecode files
|
||||
to all exist simultaneously. :func:`importlib.util.cache_from_source` has an
|
||||
updated API to help with this change.
|
||||
``.pyc`` files represent both unoptimized and optimized bytecode. To prevent the
|
||||
need to constantly regenerate bytecode files, ``.pyc`` files now have an
|
||||
optional ``opt-`` tag in their name when the bytecode is optimized. This has the
|
||||
side-effect of no more bytecode file name clashes when running under either
|
||||
``-O`` or ``-OO``. Consequently, bytecode files generated from ``-O``, and
|
||||
``-OO`` may now exist simultaneously. :func:`importlib.util.cache_from_source`
|
||||
has an updated API to help with this change.
|
||||
|
||||
.. seealso::
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue