Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
e328323c
Commit
e328323c
authored
May 26, 2015
by
Benjamin Peterson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
rephrase
parent
55871f04
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
Doc/whatsnew/3.5.rst
Doc/whatsnew/3.5.rst
+7
-7
No files found.
Doc/whatsnew/3.5.rst
View file @
e328323c
...
...
@@ -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::
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment