This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
Test Python 3.6 and Sphinx, fix documentation build, centralize dependency information #322
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
…s building to pass tests
|
I got the flake8 and Python 3.6 change into master. If you are still game, the Sphinx stuff should come in a separate pull request to keep things focused. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Documentation wasn't working due to a packaging/build issue, so
Sphinxwas upgraded from1.4.6to1.5.6.flake8replacespyflakesandpep8. No other library upgrades.Let me know if my commit that moves the requirements is a bridge too far; this PR can stand without that. But it's always rough to maintain version-pin lists in two files.