-
-
Notifications
You must be signed in to change notification settings - Fork 1
Use uv #379
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
base: master
Are you sure you want to change the base?
Conversation
|
We need to install |
|
Yes. Will do today. |
|
Done on Node 5 ... also installed /srv/python3.14 |
|
Oh, you don't need to install it, |
|
Ok ... thats nice 👍🏼 |
|
Looks good to me. Hard to really say without trying it for real. I must say I have not tried this part of Also, 3.14 will fail for any Plone version. Zope needs to be updated, and before that AccessControl, RestrictedPython and other zope packages with C code need to be updated. |
davisagli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would factor the virtualenv creation into a separate script that can be called from the others -- but it's short enough that it's fine either way.
|
To summarize my code comments: It is enough to do UV_PYTHON={py}
uv venv
uv pip install -r requirements.txt
uv run buildout .... |
|
Really I think you can just do: |
|
As a one shot as it is in Jenkins, yes. Or |
c9acb6e to
1c74258
Compare
|
Kind of off-topic, but does I recently switched from the pip API to using uv directly in Plone Sphinx Theme, and now I feel like a big boy.💪 |
|
@stevepiercy No, I don't think so. My understanding is that The |
On jenkins jobs, this simplifies so much the management of python versions that we can even test it directly on python pre-releases (3.14a4 right now) 🌟