Unindent section titles in metpy.calc docs to prevent sphinx from failing #1131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I find it hysterical that it still built the page properly. Honestly, this is the kind of resolution I was expecting. Welcome to dev life. 🤣 😱 😭 |
dopplershift
added
Area: Docs
dopplershift
approved these changes
Aug 20, 2019
This was somehow the most infuriating, but satisfying, solution I've ever come across. It was honestly a last ditch effort to just rebuild the page by sections, and a miracle happened. Yeah, if this isn't an intro to dev life, I don't know what is. |
|
Good doc build! |
|
Not sure what's up with coverage, but doesn't really matter. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description Of Changes
Unindent section headers in the
MetPy.calcdocs, so sphinx doesn't try to import them. Removes warnings in sphinx<2.2.0, removes failure in sphinx=2.2.0.I still can't believe this was all that was broken.