traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

bpo-37253: Document PyCompilerFlags.cf_feature_version (GH-14019) 

* Update PyCompilerFlags structure documentation.
* Document the new cf_feature_version field in the Changes in the C
  API section of the What's New in Python 3.8 doc.
This commit is contained in:
Victor Stinner 2019-06-13 02:01:29 +02:00 committed by GitHub
parent 468e5fec8a
commit 2c9b498759
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 20 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Doc/c-api/veryhigh.rst
View File

@ -388,11 +388,22 @@ the same library that the Python runtime is using.
Whenever ``PyCompilerFlags *flags`` is *NULL*, :attr:`cf_flags` is treated as
equal to ``0``, and any modification due to ``from __future__ import`` is
discarded. ::
discarded.
struct PyCompilerFlags {
int cf_flags;
}
.. c:member:: int cf_flags
Compiler flags.
.. c:member:: int cf_feature_version;
*cf_feature_version* is the minor Python version. It should be
initialized to ``PY_MINOR_VERSION``.
The field is ignored by default, it is used if and only if
``PyCF_ONLY_AST`` flag is set in *cf_flags*.
.. versionchanged:: 3.8
Added *cf_feature_version* field.
.. c:var:: int CO_FUTURE_DIVISION

5
Doc/whatsnew/3.8.rst
View File

@ -1312,6 +1312,11 @@ Changes in the Python API
Changes in the C API
--------------------
* The :c:type:`PyCompilerFlags` structure gets a new *cf_feature_version*
field. It should be initialized to ``PY_MINOR_VERSION``. The field is ignored
by default, it is used if and only if ``PyCF_ONLY_AST`` flag is set in
*cf_flags*.
* The :c:func:`PyEval_ReInitThreads` function has been removed from the C API.
It should not be called explicitly: use :c:func:`PyOS_AfterFork_Child`
instead.