Uh oh!
There was an error while loading. Please reload this page.
Lint: fixup subsubsection markups - #1239
Conversation
Consistently use ^ iso. ' markups for subsubsections
erlend-aasland
commented
Dec 6, 2023
Discovered over at #1238. |
hugovk
commented
Dec 6, 2023
For reference, the suggested convention is at https://devguide.python.org/documentation/markup/#sections
For this file, are we starting at |
erlend-aasland
commented
Dec 6, 2023
For which file? |
ezio-melotti
commented
Dec 6, 2023
This PR updates the headings of 8 files and, if the update follows the convention described above, then it can be approved and merged. If the other files already follow this convention, then there is nothing else to do. |
erlend-aasland
commented
Dec 6, 2023
This PR updates all files in the devguide to follow the convention described in the style guide. Does that answer your question, @ezio-melotti? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
AlexWaygood
left a comment
There was a problem hiding this comment.
LGTM other than https://github.com/python/devguide/pull/1239/files#r1417581480
hugovk
commented
Dec 6, 2023
I obviously didn't scroll very far down the diff! 😅 Let's try again: For these files, are we starting at When would we use the overlines?
If a page wants more than four levels? In that case, it would be a bit of a tricky refactor, and it's probably a good idea to avoid such deep nesting. |
erlend-aasland
commented
Dec 6, 2023
Starting at |
erlend-aasland
commented
Dec 6, 2023
Thanks for the reviews! I'll land this post house chores 🏠🗑️ |
Consistently use ^ iso. ' markups for subsubsections
📚 Documentation preview 📚: https://cpython-devguide--1239.org.readthedocs.build/