Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a single requirements file for all sessions #350

Open
cjolowicz opened this issue Apr 25, 2021 · 2 comments
Open

Use a single requirements file for all sessions #350

cjolowicz opened this issue Apr 25, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@cjolowicz
Copy link
Owner

We don't seem to need a per-session requirements file anymore. All sessions just need the full dependencies from the lock file in constraints form.

This came up a few times before:

@cjolowicz cjolowicz added the enhancement New feature or request label Apr 25, 2021
@cjolowicz
Copy link
Owner Author

One thing to keep in mind: Currently, requirements files only live as long as their environment. If it's placed outside of environments, there is no mechanism to clean up a broken requirements file. In other words, the caching will need to be more robust. For example, should we remove the file if it cannot be processed (or move it to $TMPDIR for post-mortem inspection)?

Another point, which is maybe quite specific to nox-poetry's own test suite: If poetry itself is installed inside the Nox environment, it can interfere with the exporting, with different versions of Poetry attempting to export from the lockfile. This should probably be a different issue.

@cjolowicz
Copy link
Owner Author

An implementation of this feature could use nox.Session.cache_dir introduced in Nox 2021.10.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant