Skip to content
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

Conda and pixi question #1724

Closed
amirhosseindavoody opened this issue Feb 20, 2024 · 2 comments
Closed

Conda and pixi question #1724

amirhosseindavoody opened this issue Feb 20, 2024 · 2 comments
Labels
question Asking for clarification or support

Comments

@amirhosseindavoody
Copy link

I have been using conda as my package manager for years and I thought pip is king of for the old days. Then I found pixi recently which is kind of like conda bug with more speed and more repeatability which is great.

Now, I see uv which kind of revives pip but with more speed and I am confused of the goals for each project. I have seen other questions here about benchmarking the tools but my question is about the goals of each project and technical differences.

  • I have read so many times that conda is cross language and pip is only for python. Now if we can use one cross language package manager for everything why would someone go back to language specific (like pip).

  • On the other hand, I know we can install numpy with pip which has both C and python. Then what are the cases that pip cannot handle and we need something like conda and pixi.

Sorry if the question is too fundamental but stumbling upon UV had me wondering about this for a while and I had to ask the question

@zanieb
Copy link
Member

zanieb commented Feb 20, 2024

A full answer is pretty complicated, I'll try to get to it later. In the meantime, I can point you to a couple similar questions:

@zanieb zanieb added the question Asking for clarification or support label Feb 20, 2024
@ruben-arts
Copy link

Don't mind me chiming in 🎐 .

Because conda always had a link with pip we implemented a rust version of that(rip) to integrate pip into pixi. But since we can do with uv what we could do with rip we're stopping the development on rip and will integrate uv into pixi. This way we can focus again on improving the conda-ecosystem while not leaving the python packages behind. Most of our user do indeed have your question, supporting both python c and possibly other languages.

For the pip to install of non python packages the shared libraries will get packaged up into the same wheel or are expected to be installed on the system/virtual environment. Conda on the other hand has the ability to easily package those shared libraries and install them alongside the python packages. Requiring a more minimal base installation replacing a large part of why docker is such an important development tool these days.

More info on our decision here: https://prefix.dev/blog/uv_in_pixi

@zanieb zanieb closed this as completed Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Asking for clarification or support
Projects
None yet
Development

No branches or pull requests

3 participants