| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 2cf8804 commit 4029064
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -56,7 +56,7 @@ must use the platform malloc heap(s), or shared memory, or C++ local storage or | |||
| 56 | 56 | operator new), you must first allocate the object with your custom allocator, | |
| 57 | 57 | then pass its pointer to PyObject_{Init, InitVar} for filling in its Python- | |
| 58 | 58 | specific fields: reference count, type pointer, possibly others. You should | |
| 59 | - be aware that Python no control over these objects because they don't | ||
| 59 | + be aware that Python has no control over these objects because they don't | ||
| 60 | 60 | cooperate with the Python memory manager. Such objects may not be eligible | |
| 61 | 61 | for automatic garbage collection and you have to make sure that they are | |
| 62 | 62 | released accordingly whenever their destructor gets called (cf. the specific | |
| Back | FazBrowse Home | New Git URL |
0 commit comments