You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
The text was updated successfully, but these errors were encountered: