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-100546: Remove incorrect positional-only marker from eval by hauntsaninja · Pull Request #100547 · python/cpython Conversation
|
|
Only needs backporting to 3.11 because #96579 (and subsequent partial reverts) only got backported to 3.11 (seems not particularly intentionally, seems just because automatic backporting failed) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks @hauntsaninja for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-100654 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…ythonGH-100547) All the arguments are positional-only. The current status after pythonGH-99476 seems to be to not use positional-only markers in documentation, hence I've simply removed it. (cherry picked from commit 71159a8) Co-authored-by: Shantanu <[email protected]>
All the arguments are positional-only. The current status after GH-99476 seems to be to not use positional-only markers in documentation, hence I've simply removed it. (cherry picked from commit 71159a8) Co-authored-by: Shantanu <[email protected]>
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.