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

use uv in ci #851

Merged
merged 1 commit into from
Mar 7, 2024
Merged

use uv in ci #851

merged 1 commit into from
Mar 7, 2024

Conversation

zzstoatzz
Copy link
Collaborator

No description provided.

@Zaubeerer
Copy link

Why not use https://pixi.sh/cli/ and/or rip? :)

@zzstoatzz
Copy link
Collaborator Author

Why not use https://pixi.sh/cli/ and/or rip? :)

hi @Zaubeerer - what are your favorite things about those options?

uv seems nice to me because it's real fast, mirrors pip for now, easy to work in gradually - also our friend and fellow prefect person is writing it :)

@Zaubeerer
Copy link

Hey @zzstoatzz, thanks for the quick response.

I like the idea of consolidating python package managers.
pixi seems promising as they incorporate the best of both conda and poetry while also using rust under the hood for package resolution.

I haven't used uv yet, but will try it with rye.

Just wanted to make sure you are aware of pixi and rip and was wondering about your decision points.

I just read more into rip and it seems to not be intended as a complete Python package manager yet, so I guess uv indeed is the way to go when solely focussing on pypi dependency resolution :)

@zzstoatzz zzstoatzz merged commit 58dd1a3 into main Mar 7, 2024
2 checks passed
@zzstoatzz zzstoatzz deleted the uv branch March 7, 2024 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants