GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — gh-85956: update error in documentation by koubaa · Pull Request #22242 · python/cpython Conversation
|
|
@vstinner @corona10 @shihai1991 I'm sure I have the wrong issue number but wanted to propose this change to the doc. I can change the number and rebase. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
You have the wrong issue number. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
@vstinner I made a new issue in that case. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sorry, something went wrong.
There was an error while loading. Please reload this page.
1482eab to
098273f
Compare
|
@vstinner is anything else needed before merging this? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@vstinner bump |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| declared. The sole exception are the type objects; since these must never be | ||
| deallocated, they are typically static :c:type:`PyTypeObject` objects. | ||
| declared. The sole exception are the type objects; they may be static | ||
| :c:type:`PyTypeObject` objects. |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
"The sole exception are the type objects" looks wrong to me. Almost all types in Python are allocated on the heap.
Only static types are never deallocated.
I'm not sure why these kinds of technical details are giving in an introduction. It would be better to move them to https://docs.python.org/dev/c-api/refcounting.html no?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Or at least, copied there.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Hm, I am not find the docs of PyHeapTypeObject. Maybe add those description info in it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I'm not certain what to do with this change. The whole paragraph could be revisited, as Victor hints to. I'm not sure if this change makes things clearer for the reader.
@encukou: thoughts?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
To be technically correct, it's not just types – PyModuleDef is also a PyObject* (though I assume that's for historical reasons only). But that's too much detail here.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| declared. The sole exception are the type objects; they may be static | ||
| :c:type:`PyTypeObject` objects. |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Would this work?
| declared. The sole exception are the type objects; they may be static | |
| :c:type:`PyTypeObject` objects. | |
| declared. (There are a few exceptions, like static type objects, but even those | |
| are usually manipulated via pointers.) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This has merge conflicts now.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This PR is blocked on its author, has not been touched by a human in more than 3 years, and no longer merges cleanly. Closing to cull the number of open pull requests. Do not reopen this pull request without getting a go-ahead from a triager or core developer on gh-85956. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.