-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
for python project management
#184
Comments
What does it add/improve? Install the modules in requirements-dev.txt and done. What bugs have you noticed? |
What I find a big improvement of uv over requirements[-dev].txt:
While none of these arguments on their own make a great case for adopting uv, I do think the usability and how integrated it is makes it a very useful tool to adopt. |
For me personally (and >99% of development is done by me), there is no need for uv. However, that does not mean that it's not useful for contributors. If you set up the (configuration) files uv needs to work properly and update the CONTRIBUTING.md file so that everyone can follow commands to develop using uv, then I'm fine with it. uv must not become neccesary in order to develop the project though. Just add the configuration files that need to be present so that users can initialise uv and have it be ready for use. Seems like that means some additions to the pyproject.toml file, a .python-version file and uv.lock file? |
I just forked your repo with the goal of fixing some bugs I'm seeing. The first thing that struck me is that you're not using any project manager, like poetry, pdm or uv. I've been working with uv for a while now, and I absolutely love it. It's insanely fast!
Would you be open to a PR for this?
The text was updated successfully, but these errors were encountered: