[Python-Dev] Recent changes to PyCodeObject (original) (raw)
Ned Batchelder ned at nedbatchelder.com
Wed Nov 16 19🔞16 EST 2016
- Previous message (by thread): [Python-Dev] Warnings behave differently in Python 2 and Python 3?
- Next message (by thread): [Python-Dev] Recent changes to PyCodeObject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
When I added Python 3.6 support to coverage.py, I posted a Mac wheel to PyPI: https://pypi.python.org/pypi/coverage/ That wheel was built against 3.6a3, the latest version at the time. When I use it now on 3.6b3, it doesn't work right. The reason is that the co_firstlineno field in PyCodeObject moved in September, as part of the PEP 523 work: https://github.com/python/cpython/commit/f1e6d88b3ca2b56d51d87b6b38ea1870c5d9490c
The docs say that PyCodeObject can change at any time, but I don't see why the field had to move in the first place. Was this needed?
Am I doing the wrong thing by using PyCodeObject fields directly in the coverage.py C trace function? It seems like this was an unnecessary breaking change, even if it is a non-guaranteed interface.
BTW, there are some comments that should be updated based on that commit, I can submit a patch to fix them.
--Ned.
- Previous message (by thread): [Python-Dev] Warnings behave differently in Python 2 and Python 3?
- Next message (by thread): [Python-Dev] Recent changes to PyCodeObject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]