GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |
GeezerVison is showing github.com — bpo-43693 Get rid of CO_NOFREE -- it's unused by gvanrossum · Pull Request #26839 · python/cpython Conversation
|
|
I see you've skipped the news item. I've made https://bugs.python.org/issue44500 to remind us to document all these changes. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 👍
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Python 3.11 removes this flag, see python/cpython#26839
Python 3.11 removes this flag, see python/cpython#26839
…NOFREE The constants were redefined in dis.py, and not perfectly kept in sync: inspect.CO_NOFREE was kept even though the C define went away in pythongh-26839. - Expose the constants via `_opcode` (as agreed in pythongh-68656) and its wrapper `opcode`. This removes `CO_NOFREE` from `dis.COMPILER_FLAG_NAMES`. - Re-add, deprecate and document inspect.CO_NOFREE
…NOFREE The constants were redefined in dis.py, and not perfectly kept in sync: inspect.CO_NOFREE was kept even though the C define went away in pythongh-26839. - Expose the constants via `_opcode` (as agreed in pythongh-68656) and its wrapper `opcode`. This removes `CO_NOFREE` from `dis.COMPILER_FLAG_NAMES`. - Re-add, deprecate and document inspect.CO_NOFREE
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.