Uh oh!
There was an error while loading. Please reload this page.
[3.8] [doc] Fix erroneous backslashes in signatures and names (GH-23658) - #23828
Conversation
…GH-23658) The issue being resolved is shown in the 3.10 docs (if you select docs for older versions you won't see a visual glitch). The newer sphinx version that produces the 3.10 docs doesn't treat the backslash to escape things in some situations it previously did.. (cherry picked from commit dcc997c) Co-authored-by: Andre Delfino <adelfino@gmail.com>
cbf73a3 to
246dfeeCompareandresdelfino
commented
Dec 21, 2020
@Mariatta perhaps we can merge this? |
JulienPalard
commented
Jan 3, 2021
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 ? |
andresdelfino
commented
Jan 3, 2021
@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). |
JulienPalard
commented
Jan 3, 2021
@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) |
andresdelfino
commented
Jan 3, 2021
@JulienPalard oh, yes, you are right; this should be reverted. Sorry! |
The issue being resolved is shown in the 3.10 docs (if you select docs for older versions you won't see a visual glitch).
The newer sphinx version that produces the 3.10 docs doesn't treat the backslash to escape things in some situations it previously did..
(cherry picked from commit dcc997c)
Co-authored-by: Andre Delfino adelfino@gmail.com
Automerge-Triggered-By: GH:Mariatta