I know other languages have various solutions for this (to basically have package namespaces local to a branch of the dependency tree), but I don't know how much better that experience is.
I know other languages have various solutions for this (to basically have package namespaces local to a branch of the dependency tree), but I don't know how much better that experience is.
You could try running
python -m pip check
To check dependencies. Or, python -m pip inspect
To get a JSON output of your current virtual environment.Or, update stuff automatically:
python -m pip install --upgrade
Or, skip worrying about dependencies: python -m pip install --no-deps
Or, do a dry run installation with full report on what would be installed:pip install --ignore-installed --dry-run --quiet --report
And, there's a lot more than that. Pip is pretty powerful and I'm surprised everyone dislikes it so much.
Hope this helps. Cheers!
For example, `pip install --ignore-installed --dry-run --quiet --report` will build sdists (and run arbitrary code from `setup.py` or other places specified by a build backend) - just so that it can confirm that the downloaded sdist would produce a wheel with the right name and version. Even `pip download` will do the same. I'm not kidding. There are multiple outstanding issues on the tracker that are all ultimately about this problem, which has persisted through multiple versions of the UI and all the evolving packaging standards, going back almost the entire history of Pip.
See for example https://github.com/pypa/pip/issues/1884 ; I have a long list of related reports written down somewhere.
A security researcher was once infamously bitten by this (https://moyix.blogspot.com/2022/09/someones-been-messing-wit...).
Invoking SAT with clause count: 9661561
Invoking SAT with clause count: 5164645