uv pip list does not show all packages in conda environment #3341
Comments
|
Another example. If I run: I get three warnings: But I can see these are installed in the environment: My only clue that comes out of this is that |
|
I believe this is the same underlying issue as #2500, which is (I'm guessing) those packages are located somewhere else in |
|
Thanks @charliermarsh.
Even if they are also located somewhere else in |
|
I'll take a look when I have a sec. |
|
@gboeing Could you list out the raw contents of the site-packages dir? I wonder if there's a possibility they're installed as eggs. |
|
@samypr100 here you go: |
|
Ah ok, yeah, we don't support egg-info files. |
|
@hauntsaninja -- am I right that what you requested the other day was ability to uninstall |
|
Crosslinking to #2928 |
|
Yeah, if This is getting a little off topic, but to clarify my exact request... while I certainly won't complain if you do, I'm perfectly happy for uv to not support legacy editables. The thing that I am very intrigued by is reducing the cost of editable installations going forward. Currently, with PEP 660, every editable installation creates a new I just checked and in my work environment I have ~400 projects editably installed. With the legacy editable installation, these are all in In general, I think there's opportunities for doing really nice end-to-end optimisation for editable setups if uv were to have its own build backend (e.g. installation can be instant). |
|
@hauntsaninja - thank you, exactly the info I was looking for (and understood that this is slightly different than the linked issue). |
|
I'm gonna merge this into #2928. |
|
cc @konstin regarding the workspace editables. |
|
Put up a PR to fix this: #3380 |
## Summary Users often find themselves dropped into environments that contain `.egg-info` packages. While we won't support installing these, it's not hard to support identifying them (e.g., in `pip freeze`) and _uninstalling_ them. Closes #2841. Closes #2928. Closes #3341. ## Test Plan Ran `cargo run pip freeze --python /opt/homebrew/Caskroom/miniforge/base/envs/TEST/bin/python`, with an environment that includes `pip` as an `.egg-info` (`/opt/homebrew/Caskroom/miniforge/base/envs/TEST/lib/python3.12/site-packages/pip-24.0-py3.12.egg-info`): ``` cffi @ file:///Users/runner/miniforge3/conda-bld/cffi_1696001825047/work pip==24.0 pycparser @ file:///home/conda/feedstock_root/build_artifacts/pycparser_1711811537435/work setuptools==69.5.1 wheel==0.43.0 ``` Then ran `cargo run pip uninstall`, verified that `pip` was uninstalled, and no longer listed in `pip freeze`.
This seems to be related to, but different from, #2841 and #3164. I'm using 0.1.39 on Ubuntu.
If I create a conda environment and activate it,
pip listanduv pip listshow different packages installed in the environment.So, within the TEST environment, pip can see (for example) setuptools and zstandard, but uv cannot.
The text was updated successfully, but these errors were encountered: