-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
System site-packages still not reused upon install #2287
Comments
Additionally, locking doesn't work.
Yet if I let |
As for a solution requirement: I would want the lockfile to only cover dependencies that aren't sourced from the system site-packages. The system site-packages are effectively locked through the OS package manager, whereas the other dependencies aren't if I forego locking during build. |
Another interesting case that can't be worked around by using
It seems |
I don't know if you understand the trickery in https://sourceforge.net/p/ruamel-yaml/code/ci/default/tree/setup.py, @frostming ... I'm out of my depth. |
The dependencies will always be resolved whether they are included by system-site-package or not. Even when writing lockfile is not required(--no-lock). This step is mandatory to make sure the dependencies are compatible with each other. The system site packages Can only skip the installation of packages if its version matches exactly with the one in the lockfile. |
For context, does Poetry have the same behavior? |
@frostming I fail to wrap my head around how to reuse system site-packages with PDM. If I remove/disregard the lockfile and my dependency has a dependency with a lower bound version range, then the latest version will be collected from the package index, whereas my system site-package version is lower but still compatible with the lower bound version range. How to avoid this issue? |
This was resolved by the introduction of |
Make sure you run commands with
-v
flag before pasting the output.Steps to reproduce
See below.
pyproject.toml
snippet:Actual behavior
Expected behavior
PDM doesn't try to install packages that are already available in the venv through system site-packages (#2216).
Environment Information
See previous log.
The text was updated successfully, but these errors were encountered: