Migrate deps to setup.cfg
#247
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
Modern python packaging uses `setup.cfg`. Historically we had our deps in `setup.py` due to GitHub's dependency graph, but they've since added support for parsing deps out of `setup.cfg`. Also, this allows us to start specifying the Sphinx theme as a `docs` extra... this is much more idiomatic than bundling it as a git submodule.
|
Oof, I'm behind the times... apparently |
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.
Modern python packaging uses
setup.cfg. Historically we had our deps insetup.pydue to GitHub's dependency graph, but they've since added support for parsing deps out ofsetup.cfg.Also, this allows us to start specifying the Sphinx theme as a
docsextra... this is much more idiomatic than bundling it as a git submodule. And will later make it much simpler for RTD etc to pull in the custom theme.