Cache exported requirements in Nox sessions#491
Merged
Conversation
added 2 commits
August 2, 2020 11:49
The `--no-root` option allows installing core dependencies without the package itself, so it is no longer necessary to export requirements and install with pip.
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.
This PR speeds up Nox runs by exporting requirements only when the lock file changes. The requirement files are cached in the per-session temporary directory introduced in Nox 2020.5.24. As a consequence, requirements are only reused as long as the Nox environments are reused (
--reuse-existing-virtualenvs).As a side effect, the requirements file for
safetyis no longer generated without hashes.safetyappears to handle requirements files with hashes just fine.