pixi remove python doesn't remove uv dependencies

[wolfv]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

pixi init bla
cd bla
pixi add python
pixi add --pypi flask
pixi remove python

Issue description

We have a crash because pixi first removes Python, and then still tries to create a uv context (which needs a Python interpreter).

I am not sure what we should do:

• Disallow removing python when pypi-dependencies are there
• Remove all pypi-dependencies when python gets removed (might destroy some work, we could add a yes/no prompt)
• Just keep the uv stuff as is?

I think right now I prefer option 1, actually.

Expected behavior

Unsure, but don't crash!

[ruben-arts]

I hate special cases for python but this does make sense to me, I think it makes sense to fix this with the prompt e.g.:

> pixi remove python
× You can't remove python if you have `pypi-dependencies`.

Do you want me to also remove all `pypi-dependencies`?
> yes
- no

But to fix it quickly disallowing it for now is a good first step.

[olivier-lacroix]

I feel like removing all pypi-dependencies to keep it consistent and not special-case python would also be acceptable. what work could it destroy @wolfv ?

[tdejager]

I agree with @olivier-lacroix here :) but would be good to hear if it actually destroys something.

[ruben-arts]

I would also be fine with not having a prompt, as it can always be added if it is not comfortable enough.

> pixi remove python
x Removing python also removes all [pypi-dependencies] from your environment.
 |
 -> Removed flask, click, tensorflow, xxx