Skip to content
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

bpo-40989: Make _PyTraceMalloc_NewReference() internal #20915

Merged
merged 1 commit into from Jun 16, 2020

Conversation

Copy link
Member

@vstinner vstinner commented Jun 16, 2020

Make the _PyTraceMalloc_NewReference() function fully internal:
remove it from the public C API and don't export it anymore.

https://bugs.python.org/issue40989

Make the _PyTraceMalloc_NewReference() function fully internal:
remove it from the public C API and don't export it anymore.
@vstinner
Copy link
Author

@vstinner vstinner commented Jun 16, 2020

At the second build, the 3 mandatory Travis CI jobs passed, but I have to wait until the two optional coverage jobs are running before being able to merge.

I created https://bugs.python.org/issue40993 "Don't run Python and C coverage jobs of Travis CI on pull requests" to be able to merge PRs faster.

@vstinner vstinner merged commit fcc60e4 into python:master Jun 16, 2020
9 checks passed
@vstinner vstinner deleted the make_tracenew_ref_internal branch Jun 16, 2020
J-Arun-Mani pushed a commit to J-Arun-Mani/cpython that referenced this issue Jul 21, 2020
Make the _PyTraceMalloc_NewReference() function fully internal:
remove it from the public C API and don't export it anymore.
chrisburr pushed a commit to chrisburr/cpython that referenced this issue Dec 9, 2020
Make the _PyTraceMalloc_NewReference() function fully internal:
remove it from the public C API and don't export it anymore.
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.

None yet

3 participants