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
When updating requirements (e.g. via pdm update --update-eager) it should not automatically sync/install dependencies.
pdm update --update-eager
(My use case here is using pdm for managing dependencies, but would like to install them only via exported requirements.txt files then.)
requirements.txt
Note that pdm update --update-eager --dry-run looks like the following, creating a __pypackages__ skeleton:
pdm update --update-eager --dry-run
__pypackages__
✔ 🔒 Lock successful Packages to add: … % find __pypackages__ __pypackages__ __pypackages__/3.9 __pypackages__/3.9/lib __pypackages__/3.9/include __pypackages__/3.9/bin __pypackages__/.gitignore
--no-sync exists with pdm-add already, and appears to make sense here then also.
--no-sync
The text was updated successfully, but these errors were encountered:
What is the problem of --dry-run? Do you want to update the lock file but not install them?
--dry-run
Sorry, something went wrong.
Do you want to update the lock file but not install them?
Yes.
update
Successfully merging a pull request may close this issue.
When updating requirements (e.g. via
pdm update --update-eager
) it should not automatically sync/install dependencies.(My use case here is using pdm for managing dependencies, but would like to install them only via exported
requirements.txt
files then.)Note that
pdm update --update-eager --dry-run
looks like the following, creating a__pypackages__
skeleton:--no-sync
exists with pdm-add already, and appears to make sense here then also.The text was updated successfully, but these errors were encountered: