scripts: update pyproject.toml - deprecated poetry config + support uv #13615
+1,205
−159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
I was trying to run some scripts and realised uv would not install the dependencies from
pyproject.toml
, as it could not find the standard[project]
section.Furthermore, poetry itself would complain about some deprecated fields:
In this PR I updated the existing
pyproject.toml
files to use the most recent standard format, usinguvx migrate-to-uv
-while keeping the non-standard poetry fields, too. If I did everything correctly, this should be backwards compatible. 🙂 Although I'd happily provide another PR to switch to uv in CI, too.I found #11597 is also solving this problem in a different way, but I believe this change to
pyproject.toml
would be needed sooner or later, anyway, since Poetry is also correctly deprecating their own configuration in favour of the standard one. And so even if sticking to Poetry, at some point that would also fail.