-
Notifications
You must be signed in to change notification settings - Fork 210
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
Pixi removing packages installed by uv
not part of pixi.toml
#998
Comments
He @tadejsv, this is an good find. @tdejager I know we're going to support all this behavior but would it be possible to make sure we only uninstall pixi installed packages? By making the |
I made a quick PR to |
I agree I think that would be the only option, it can potentially keep
brealking for newer versions of pixi as long as people have not cleared
their environments so we might need to add something to the release notes
for that.
Let’s hope uv accepts that PR soon :)
…On Wed, 20 Mar 2024 at 11:24, Wolf Vollprecht ***@***.***> wrote:
I made a quick PR to uv here: astral-sh/uv#2561
<astral-sh/uv#2561>
—
Reply to this email directly, view it on GitHub
<#998 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADF4XS73B7B4JL6DHU4WODYZFPVDAVCNFSM6AAAAABEZS553GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGIYTMNZUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Uv has merged this so we should update and add the installer in the relevant places :) |
Check the INSTALLER when removing packages either through changing of dependencies or python version. Fixes: #998 We now have the following behavior: * If the installer is not `uv-pixi` and not managed by pixi we do not touch the package. * If the installer is not `uv-pixi` but is managed by pixi we re-install. Also, In the case where we switch python interpreters, which requires a new `site-packages` folder: * We leave the packages alone that do not have our installer Co-authored-by: Ruben Arts <[email protected]>
I am installing a package from github (
git+ssh://
) usinguv
, as pixi does not support this yet. However, whenever I run anypixi
command (even justpixi shell
), this package gets uninstalled.Is this really the desired behavior? Why not just issue a warning if non pixi-managed package is found? Or at least give an option to disable this behavior?
For now I am simply switching to installing with
pip
, which works, but is inferior to installing withuv
The text was updated successfully, but these errors were encountered: