We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
--check-updates
When you call fades with a file dependency (like, fades -d file:///tmp/path/to/project) it will not re-create the venv even if the project changes.
fades
fades -d file:///tmp/path/to/project
We could store the directory ctime in the fades metadata file, and use it to check updates and re-create the venv if changed.
ctime
This would be an example of use sequence:
fades --check-updates -d file:///tmp/path/to/project
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When you call
fades
with a file dependency (like,fades -d file:///tmp/path/to/project
) it will not re-create the venv even if the project changes.We could store the directory
ctime
in the fades metadata file, and use it to check updates and re-create the venv if changed.This would be an example of use sequence:
fades -d file:///tmp/path/to/project
: a venv is created first timefades -d file:///tmp/path/to/project
: the venv is reusedfades -d file:///tmp/path/to/project
: the venv is just reused!fades --check-updates -d file:///tmp/path/to/project
: the project's dirctime
changed! a new venv is createdfades --check-updates -d file:///tmp/path/to/project
: the project's dirctime
didn't change, the venv is reusedfades --check-updates -d file:///tmp/path/to/project
: the project's dirctime
changed! a new venv is createdThe text was updated successfully, but these errors were encountered: