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 — [3.8] [doc] Fix erroneous backslashes in signatures and names (GH-23658) by andresdelfino · Pull Request #23828 · python/cpython Conversation
|
|
@Mariatta perhaps we can merge this? |
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
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.
Thanks
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
As in the 3.8 and 3.9 branch we don't use the newer Sphinx, this commit drops the backslashes :( I think this should be reverted, are you ok for a revert @andresdelfino ? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@JulienPalard this commit doesn't affect how the doc is rendered for 3.8/3.9, but I think it's good to have consistency with master (to prevent conflicts for future commits). |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@andresdelfino I just tried locally a first build on the top of 3.9, I have: and then reverted e89993c, build again, and I now have: so looks like e89993c made the backslash dissapear (see here in prod: https://docs.python.org/3.9/library/functions.html#print) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@JulienPalard oh, yes, you are right; this should be reverted. Sorry! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
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.