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
Make sure you run commands with -v flag before pasting the output.
Steps to reproduce
Case 1:
In an empty project, set:
requires-python = ">=3.7"
Then:
pdm install
pdm add pandas==1.3.4 -v
You can see that the output loops for a little while, mostly on numpy constraints, but pdm ultimately accurately decides that pandas requires Python 3.7.1, not 3.7, and prints this. This is good.
This appears to be too much for pdm. It loops for a few minutes printing again mostly numpy constraints, until I cancel it.
Projects are often much bigger than 1 package, and if only 2 packages are able to confuse the dependency resolver, that is not good.
The workaround is of course, you can find out through external means that certain packages have minimum Python version requirements, and adjust your config accordingly.
Actual behavior
Pdm completes but is a bit slow for Case 1.
Pdm loops indefinitely for Case 2.
Expected behavior
Pdm completes fast for Case 1.
Pdm completes fast for Case 2.
Environment Information
It is actually version 1.11.0 through homebrew, and there is an open bug about 0.0.0 printing.
It is similar to these two bugs, although not identical, because they have already been fixed, and I have a version of pdm with those fixes merged.
#627
#744
Make sure you run commands with
-v
flag before pasting the output.Steps to reproduce
Case 1:
In an empty project, set:
Then:
You can see that the output loops for a little while, mostly on numpy constraints, but pdm ultimately accurately decides that pandas requires Python 3.7.1, not 3.7, and prints this. This is good.
Case 2:
However, if instead of an empty project, you had:
Then again you do:
This appears to be too much for pdm. It loops for a few minutes printing again mostly numpy constraints, until I cancel it.
Projects are often much bigger than 1 package, and if only 2 packages are able to confuse the dependency resolver, that is not good.
The workaround is of course, you can find out through external means that certain packages have minimum Python version requirements, and adjust your config accordingly.
Actual behavior
Pdm completes but is a bit slow for Case 1.
Pdm loops indefinitely for Case 2.
Expected behavior
Pdm completes fast for Case 1.
Pdm completes fast for Case 2.
Environment Information
It is actually version 1.11.0 through homebrew, and there is an open bug about 0.0.0 printing.
Thanks for working on this tool!
The text was updated successfully, but these errors were encountered: