| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good. I've one concern about code organization, but that's all.
Sorry, something went wrong.
|
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 I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
I have made the requested changes; please review again. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @markshannon: please review the changes made to this pull request. |
Sorry, something went wrong.
|
Friendly ping, @markshannon @Fidget-Spinner . |
Sorry, something went wrong.
There was a problem hiding this comment.
Just two questions
Sorry, something went wrong.
| _PyStackRef_AsTuple(_PyStackRef ref, PyObject *op) | ||
| { | ||
| // Do not check StackRef flags in the free threading build. | ||
| return Py_BuildValue("(ni)", Py_REFCNT(op), -1); |
There was a problem hiding this comment.
Actually, I've realized that we could remove this special case.
It's related only to stackrefs for immortal objects at ft build.
We can make a little change for _PyStackRef_FromPyObjectSteal and for PyStackRef_FromPyObjectNew function: add Py_TAG_DEFERRED flag to references on immortal objects.
All tests passed with this change on my machine.
But I suggest doing this in the next small PR, and keep only tests changes here.
Sorry, something went wrong.
There was a problem hiding this comment.
I've created a #141675 for this change.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks!
Sorry, something went wrong.
|
CC @markshannon @Fidget-Spinner @colesbury Another option is merge #143024 first and adapt tests for that change here. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
New test file Lib/test/test_stackrefs.py introduced.
Some auxillary functions are added to _testinternalcapi.
Those functions are examples of correct StackRef scenarios.
We check that all refcounts remain correct.
And that results are the same for equivalent scenarios.