Use PEP508-style requirements, supported by both pip and install_requires #92
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
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.
The
git+https://github.com/amCap1712/mbdata.git@upstream-schema-changes#egg=mbdatasyntax isn't supported when this value is ininstall_requiresin setup.py.This caused problems when another project imported BU as a dependency, resulting in a failure to clone the mbdata fork that we're currently using for schema 27.
recent pip also supports installing from a PEP-058 specification, so just switch to that in requrements.txt. This is copied into setup.py and works fine when installing transitive dependencies.