Skip to content

There's no information about uv in the comparison of packaging tools #499

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

Open
MarieRoald opened this issue May 19, 2025 · 0 comments
Open
Labels
help wanted We welcome a contributor to work on this issue! thank you in advance! sprintable

Comments

@MarieRoald
Copy link
Contributor

It would be helpful with some information about uv in the build system comparison (or at least a banner that acknowledges that uv exists and that it will be added to this list soon or when the build backend is out of preview).

There are a couple of gotcha’s with uv:

  • Libraries in the virtual environments are hardlinked, so if multiple environments have the same version of the same library, then the files in the venv are hardlinked by default, so a change in one venv will affect the other. (This is only a problem if you edit modules in site-packages).
  • Uv will not compile dependencies to bytecode by default, so the first time you import a module, it takes longer. This is not a problem for development, but if anyone is containerising their app, then they should be aware of this.
@lwasser lwasser added help wanted We welcome a contributor to work on this issue! thank you in advance! sprintable labels May 19, 2025
@lwasser lwasser moved this to Python Package Guide in pyOpenSci Help Wanted Project Board May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted We welcome a contributor to work on this issue! thank you in advance! sprintable
Projects
Status: Python Package Guide
Development

No branches or pull requests

2 participants