CI: Update dependency installation order #86
Merged
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
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.
A quick fix to prevent the pip dependency resolver from borking when trying to install jupytext and myst-nb sequentially.
A bit of background:
The motivation for keeping two separate requirements files is that the requirements that are needed to build the website (
site/requirements.txt) are not required in order to simply run the tutorials as jupyter notebooks locally (as one would do either on their own machine or binder). However, the dependency management between myst-nb and jupytext has caused problems in the past: see executablebooks/MyST-NB#289 and executablebooks/MyST-NB#333). This reordering avoids the problem reported in the latter.