8000 bpo-39542: Make _Py_NewReference() opaque in C API by vstinner · Pull Request #18346 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content
8000

bpo-39542: Make _Py_NewReference() opaque in C API #18346

New issue

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 1 commit into from
Feb 5, 2020
Merged

bpo-39542: Make _Py_NewReference() opaque in C API #18346

merged 1 commit into from
Feb 5, 2020

Conversation

vstinner
Copy link
Member
@vstinner vstinner commented Feb 4, 2020

_Py_NewReference() becomes a regular opaque function, rather than a
static inline function in the C API (object.h), to better hide
implementation details.

Move _Py_tracemalloc_config from public pymem.h to internal
pycore_pymem.h header.

Make _Py_AddToAllObjects() private.

https://bugs.python.org/issue39542

_Py_NewReference() becomes a regular opaque function, rather than a
static inline function in the C API (object.h), to better hide
implementation details.

Move _Py_tracemalloc_config from public pymem.h to internal
pycore_pymem.h header.

Make _Py_AddToAllObjects() private.
@vstinner vstinner merged commit 40e547d into python:master Feb 5, 2020
@vstinner vstinner deleted the py_newreference branch February 5, 2020 00:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0