Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upbpo-39153: Clarify refcounting semantics #18220
Open
+14
−6
Conversation
This comment has been minimized.
This comment has been minimized.
Thanks @nanjekyejoannah; I can't tell you how many times I've had to dig through the source code to remember this! |
This comment has been minimized.
This comment has been minimized.
@ncoghlan and @serhiy-storchaka , if this looks fine, I will merge it. |
@nanjekyejoannah |
Misc/NEWS.d/next/Documentation/2020-01-27-22-24-51.bpo-39153.Pjl8jV.rst
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
nanjekyejoannah commentedJan 27, 2020
•
edited by bedevere-bot
Clarify refcounting semantics for the following functions:
https://bugs.python.org/issue39153