Make new release (PyPI etc.)

[mikez]

As part of the release, briefly summarize any major changes compared to the previously released version.

[AlexanderWillner]

As the release workflow is part of uv, we might want to address #134 first

[mikez]

@AlexanderWillner How is the release workflow part of uv? (My understanding is that uv is a package installer and resolver, with its chief benefit being build speed.)

[AlexanderWillner]

https://docs.astral.sh/uv/guides/package/#publishing-your-package

[mikez]

Is this essentially what make upload does? (i.e. twine.)

[AlexanderWillner]

Yes, astral-uv can replace pip (partial), setuptools, flit, poetry, twine, and parts of virtualenv and tox.

[mikez]

As said earlier, it seems the chief utility of uv is build speed (since it uses Rust), but that's not really an issue for this project. For sustainability and maintainability, I much more trust the tools maintained by the Python Software Foundation. I think adding a wrapper around the built-in tools here is overkill; I prefer minimal dependencies unless it has a clear use case.

[mikez]

If you do want to make things more "modern", you could check out pyproject.toml.
For inspiration, see flask, pandas, or requests.

[mikez]

@AlexanderWillner Shall we set a deadline for release?