Changes between Initial Version and Version 1 of Ticket #14952, comment 3


Ignore:
Timestamp:
03/01/2012 10:33:07 AM (3 years ago)
Author:
carljm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14952, comment 3

    initial v1  
    22> Do you have a source for "executing Python bytecode only files is gradually being removed from CPython"? There are no PEPs pertaining to removing the bytecode generation step for CPython.
    33
    4 [PEP 3147 http://www.python.org/dev/peps/pep-3147/] doesn't remove bytecode generation, but it moves the `pyc` files into a `__pycache__` subdirectory, and this is already implemented in Python 3. So adding any code to Django that explicitly look for `pyc` files next to the `py` file is adding code that we already know to be obsolete. This is just reinforcement of the point that bytecode files are an internal CPython implementation detail, and not something that other code should be looking at directly.
     4[http://www.python.org/dev/peps/pep-3147/ PEP 3147] doesn't remove bytecode generation, but it moves the `pyc` files into a `__pycache__` subdirectory, and this is already implemented in Python 3. So adding any code to Django that explicitly look for `pyc` files next to the `py` file is adding code that we already know to be obsolete. This is just reinforcement of the point that bytecode files are an internal CPython implementation detail, and not something that other code should be looking at directly.
Back to Top