🚒 switched to pip-compile#7
Open
stevejpurves wants to merge 1 commit into
Open
Conversation
stevejpurves
force-pushed
the
feat/pip-compile
branch
from
789af51 to
09ae060
Compare
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
1 participant
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.
Whilst working on the submission documentation.
I've been reviewing how we should recommend people provide pinned dependencies and in this PR have switched to using
pip-compilealong withrequirements.inand am suggesting for the MVP that we ask people to use pip alone for the submissions rather thanpiporconda.Happy to expand that as needed though, as there is a different workflow that can be achieved with
condaalthough a little more clunkly.Proposal is we make the templates
pip/pip-compilefirst.and a question is should we support (additional automated checks) and document a second supported conda route for people?