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 — bpo-40170: Hide implementation detail of Py_TRASHCAN_BEGIN macro by shihai1991 · Pull Request #23235 · python/cpython Conversation
|
|
cc @vstinner |
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 an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
| * The ``Py_TRASHCAN_BEGIN`` macro no longer accesses PyTypeObject attributes, | ||
| but now can get the condition by calling the new private | ||
| :c:func:`_PyTrash_cond()` function which hides implementation details. | ||
| (Contributed by Hai Shi in :issue:`40170`.) |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I don't think that it's worth it to mention in What's New in Python 3.10. End users will not notice and don't care ;-)
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.
Ok, removed.
I decided add this news because I saw you have written the description info of _PyTrash_begin() and _PyTrash_end() in whatsnew. Lol~
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 wrote a changelog entry, but nothing in What's New in Python 3.9 or What's New in Python 3.10, 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.
Oh, I saw this info in https://github.com/python/cpython/blob/master/Misc/NEWS.d/3.9.0a5.rst.
Looks like I confused the news file with relese file : (, sorry.
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.
No problem.
I consider that "What's New in Python X.Y" should be short and only describe the public API, but the Changelog should describe every single change and private functions can be mentioned there.
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.
Oh, This great. I am very confused when I start write the whatsnew file in the first time.
It's more like a double copy operation.
In fact, I don't know how release manager to archieve those change log.
My simple thought: Maybe we can create some labels to tag what's info should be added in release file or not. When release manager archive those change log, those taged changeinfo chould be archieved in release file automatically.
If this thought have any value, I can add this in my TODO list. Lol~
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 an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@vstinner Hi, victor. Is this PR good enough to be merged? |
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.
LGTM, but please address my last minor request (just add a comment).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| } | ||
|
|
||
|
|
||
| int |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Please add comment explaining that it is used by the Py_TRASHCAN_BEGIN macro.
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.
Got it, updated.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Merged, thanks. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks, victor. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
The Py_TRASHCAN_BEGIN macro no longer accesses PyTypeObject attributes, but now can get the condition by calling the new private _PyTrash_cond() function which hides implementation details.
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.