-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update .pre-commit-config.yaml to use uv #108
Comments
This one is going to be tricky and take some thinking I believe. The current issues aren't related to For the error in CI it looks like it is no longer finding the |
I haven't had a chance to test this yet, but I'm wondering if we update dependencies if it could fix at least some of the issues. Since 3.13 has been released there should be wheels available for at least some of them by now. It might not fix everything, but it seems like a good place to start |
I haven't had the time to test this yet either 🤣. I think you're right, Python 3.13 should be more or less stable to use. My problem is that the ML libraries I tend to use (Scipy, numpy, PyTorch, etc.) don't track newer versions of Python very well, so I normally wait a year or so till I upgrade Python versions, until these libraries catch up. That being said, uv isn't running system Python, right? Is there a reason why we can't update the pre-commit to also use the uv-managed version of Python? In your case, say you installed Python 3.13 via uv: |
I’m not using For CI we are using pre-commit.ci to run the |
We should upgrade the
.pre-commit-config.yaml
in this repo to useuv
so that we can run mypy prior to pushing changes. Something like the below:https://github.com/smarlhens/python-boilerplate/blob/main/.pre-commit-config.yaml
The text was updated successfully, but these errors were encountered: