I know you got your answer to why the change occurred, but a patch to update any outdated comments would be appreciated. :)
On Thu, 17 Nov 2016 at 07:55 Ned Batchelder <n...@nedbatchelder.com> wrote: > On 11/17/16 10:09 AM, Cody Piersall wrote: > > On Wed, Nov 16, 2016 at 6:18 PM, Ned Batchelder <n...@nedbatchelder.com> > wrote: > >> 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? > > Christian Heimes had the idea so that memory consumption wouldn't be > > impacted by adding co_extra to the struct: > > https://mail.python.org/pipermail/python-dev/2016-August/145961.html > > > > Thanks, I should have searched :) > > --Ned. > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
