Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
10e46444
Commit
10e46444
authored
Sep 05, 1997
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix in trailing comment: PyDict_SetItemString() does *not* consume a reference
count, PyList_SetItem() does. Very confusing!
parent
614aaf7e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
3 deletions
+2
-3
Include/object.h
Include/object.h
+2
-3
No files found.
Include/object.h
View file @
10e46444
...
@@ -461,9 +461,8 @@ quickly. Thus, to retrieve an object and store it again, the caller
...
@@ -461,9 +461,8 @@ quickly. Thus, to retrieve an object and store it again, the caller
must call Py_INCREF() explicitly.
must call Py_INCREF() explicitly.
NOTE: functions that 'consume' a reference count like
NOTE: functions that 'consume' a reference count like
PyDict_SetItemString() even
PyList_SetItemString() even consume the reference if the object wasn't
consume the reference if the object wasn't stored, to simplify error
stored, to simplify error handling.
handling.
It seems attractive to make other functions that take an object as
It seems attractive to make other functions that take an object as
argument consume a reference count; however this may quickly get
argument consume a reference count; however this may quickly get
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment