Uh oh!
There was an error while loading. Please reload this page.
GH-132775: Fix argument parsing for _interpqueues.put() - #137686
Conversation
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
ericsnowcurrently
commented
Aug 21, 2025
Just be sure I understood, the problem is that the arg spec for I'm pretty sure the FWIW, at the time, with the feature freeze at hand, I didn't worry about ironing out little API quirks (e.g. placeholder args) in the low-level module. It isn't exposed to users, right? Footnotes
|
ericsnowcurrently
commented
Aug 21, 2025
To be clear, I left room for other "fallback" options later, rather than it being a definite binary choice. Sorry that wasn't more clear. Then again, that decision was probably a premature accommodation for a possible future. I figure it doesn't matter much though. |
This comment was marked as resolved.
This comment was marked as resolved.
AA-Turner
commented
Aug 21, 2025
Yes, specifically that the format spec for
I've updated the PR. I don't think we need the test anymore given this is the current behaviour -- we are just removing the errant
Definitely the correct choice. A |
Uh oh!
There was an error while loading. Please reload this page.
Thanks @AA-Turner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
…thonGH-137686) (cherry picked from commit 79aeeb8) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
GH-138034 is a backport of this pull request to the 3.14 branch. |
serhiy-storchaka
commented
Aug 22, 2025
And I think that it would be better to remove passing explicit -1 as the fallback argument to |
…)`` (pythonGH-137686) (python#138034) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Bug introduced in #134440, cc @serhiy-storchaka@ericsnowcurrently. Also xref gh-137685.
A