8000 bpo-39562: Prevent collision of future and compiler flags by isidentical · Pull Request #19230 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

bpo-39562: Prevent collision of future and compiler flags #19230

New issue 8000

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Apr 22, 2020
Prev Previous commit
Next Next commit
Mention clashing variables, remove old comment
  • Loading branch information
isidentical committed Apr 20, 2020
commit 560a100ba25bb46ad8031aadf12fb969136b013c
3 changes: 2 additions & 1 deletion Doc/whatsnew/3.9.rst
Original file line number Diff line number Diff line change
Expand Up @@ -828,7 +828,8 @@ Changes in the Python API
(Contributed by Serhiy Storchaka in :issue:`40257`.)

* The constant values of future flags in the :mod:`__future__` module
is updated in order to prevent collision with compiler flags.
is updated in order to prevent collision with compiler flags. Previously
``PyCF_ALLOW_TOP_LEVEL_AWAIT`` was clashing with ``CO_FUTURE_DIVISION``.
(Contributed by Batuhan Taskaya in :issue:`39562`)

CPython bytecode changes
Expand Down
1 change: 0 additions & 1 deletion Include/code.h
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,6 @@ typedef struct {
#define CO_ITERABLE_COROUTINE 0x0100
#define CO_ASYNC_GENERATOR 0x0200

/* These are no longer used. */
/* bpo-39562: These constant values are changed in Python 3.9
to prevent collision with compiler flags. */
#define CO_FUTURE_DIVISION 0x20000
Expand Down
0