Fix sphinx build issues; add better travis fold reporting; update aut… #1448
Conversation
This file contains hidden or 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
tannewt
approved these changes
Jan 9, 2019
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.
recommonmarkupdated versions a day ago, which made it stop working with the older version of sphinx (Sphinx<1.8.0) we were specifying in .travis.yml. This removes the version restrictions, and reworks some internal links inports/nrf/README.mdthat were the only things that were failing with the newer versions.I tried various features of
recommonmarkincludingAutoStructify, but was unable to get these links to work. These links were already broken in RTD anyway (they pointed to theREADME.mdinstead of the generatedREADME.html).Added a simple idiom and printing script to allow commands inside folds to save their status and then print it out after the fold.
Removed MicroPython-specific authors from author lists in
conf.pyto avoid confusion about who is responsible for CircuitPython documentaiton.