Skip to content

Switch to uv for version management#857

Closed
FichteFoll wants to merge 8 commits into
masterfrom
feature/uv
Closed

Switch to uv for version management#857
FichteFoll wants to merge 8 commits into
masterfrom
feature/uv

Conversation

@FichteFoll

Copy link
Copy Markdown
Collaborator

As discussed in #826 already, we wanted to switch from poetry to uv, so here it is.

Must have happened a while ago, actually.
Instead of using `poetry` for everything, we now provide the generic
PEP-621 project metadata, use `hatchling` as the build backend and
recommend `uv` as our version manager.

This is a breaking change for packagers.
This does not do compilation. A proper linter should be set up for this
but trying to get it to pass is likely to cause conflicts with open
pull requests, so it is deferred until later.
Docker image has not been updated in 5 years and nixOS flake has moved.
By telling uv to use the oldest supported Python version, it is easier
to ensure that we did not break anything accidentally when running it
locally.
@FichteFoll

FichteFoll commented Jul 12, 2026

Copy link
Copy Markdown
Collaborator Author

Redacting this PR because it contains a lot of "code" generated by LLMs which @z411 has expressed rejection for.

@FichteFoll FichteFoll closed this Jul 12, 2026
@FichteFoll
FichteFoll deleted the feature/uv branch July 13, 2026 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant