Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Sorry, something went wrong.
There was a problem hiding this comment.
overall this looks good, only a minor Python code modernization suggestion.
I do think your second bullet from the bug "If function _PyArg_ParseStack parses failed, assign all the parsed arguments to "NULL" after they are freed, this should be done in _PyArg_ParseStack." is also worth doing to make bugs like this less likely to occur. That can be done in its own PR.
Sorry, something went wrong.
|
Of particular note, since the generated files check in CI passed, does that mean we don't have any actual standard library argument clinic uses of this str conversion via codec functionality yet? |
Sorry, something went wrong.
|
does that mean we don't have any actual standard library argument clinic uses of this str conversion via codec functionality yet? Yes, I have searched this in CPython source code and didn't find any usage of argument clinic str conversion with "encoding" parameter setting. And test for this functionality is added in #96178, which has not been merged yet. |
Sorry, something went wrong.
|
Also, my preference, as stated in #96178 (comment), would be to first merge that PR (with a minimal test suite), and then for each bugfix PR (such as this one) add both the bugfix and the complementing test. So, I'm suggesting putting this on hold until #96178 is merged. |
Sorry, something went wrong.
|
Added Argument Clinic functional test (#96002). |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM with minor nitpicks :)
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks!
Sorry, something went wrong.
|
I do think your second bullet from the bug "If function _PyArg_ParseStack parses failed, assign all the parsed arguments to "NULL" after they are freed, this should be done in _PyArg_ParseStack." is also worth doing to make bugs like this less likely to occur. That can be done in its own PR. @colorfulappl, are you up for fixing _PyArg_ParseStack while you're at it? |
Sorry, something went wrong.
|
are you up for fixing _PyArg_ParseStack while you're at it? I have not started yet, but I am willing to have a try. :) |
Sorry, something went wrong.
|
Status check is done, and it's a success ✅. |
Sorry, something went wrong.
|
GH-100352 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
|
GH-100353 is a backport of this pull request to the 3.10 branch. |
Sorry, something went wrong.
Fix double-free bug mentioned at #99240,
by moving memory clean up out of "exit" label.
Automerge-Triggered-By: GH:erlend-aasland