Add sphinx support - pydotorg compat (ref #1385) #1569
Closed
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
- RFC2822 headers work - Contents page generated - Title autogeneration not working - PEP 0 not started
Also add pep_parser as I missed it
- exclude contents in transforms - add custom text in contents.rst
- RtD still runs sphinx 1.8.5 so we have had to add compatibility
Contains: - core, - package.py
Co-authored-by: Pradyun Gedam <[email protected]>
|
Closing (xref #1385 reason for closing) |
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.
See #2, #1385 for context.
This is the core Sphinx support part, comprising
Note - this is a temporary compat layer to check that both pydotorg and Sphinx/GH-pages can be driven from the same back-end, this isn't intended to be used as an end product
Note: this is unlikely to successfully build, I am splitting into logical chunks as per Victor's comment.