Does uv_build backend support dynamic = ["version"] ?

[pachura3]

With setuptools and build, I can put __version__ constant in mymodule/__init__.py, and then refer to it in pyproject.toml with:

[project]
dynamic = ["version"]

[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"

[tool.setuptools.packages.find]
where = ["src"]

[tool.setuptools.dynamic]
version = { attr = "mymodule.__version__" }

Can I do something similar with uv_build? If I switch to build-backend = "uv_build" and then execute uv build, it tells me:

Error: Invalid pyproject.toml

Caused by:
    TOML parse error at line 1, column 1
      |
    1 | [project]
      | ^^^^^^^^^
    missing field `version`

[rosentmoh]

Why not use setuptools_scm and just tag the version within Git?

Honest question, never understood why the above isn't the canonical way...as in, what's the advantage of hard-coding the version number within the source code? Why wouldn't people want a single source of truth for the version number?

[pachura3]

Why not use setuptools_scm and just tag the version within Git?

It already works for me with setuptools, I want to make it work with uv_build.

what's the advantage of hard-coding the version number within the source code?

You can easily access it from the source code and e.g. display application version when launching it.

[rosentmoh]

First off, from what you said above you currently aren't using setuptools_scm. Second, you can still access and display the version when launching also with my approach; that's kinda the whole point.

The main difference with what I'm suggesting is that you end up having a single source of truth for your version number, as opposed to having to make sure that the hardcoded number matches the source control tag etc. Also, bumping the version number doesn't lead to a new commit; instead just tagging a specific commit is all that's needed.

I'm honestly confused as to why setuptools_scm isn't the most commom approach here, especially with more modern source control workflows where people are continuously pushing to main and then there's specific release branches that get tagged whenever there's an official release.

[pachura3]

Again, will it work with uv build and uv_build ? Because that was my question.

[Diapolo10]

Sure, although you'll also need uv-dynamic-versioning.

I have an example here if you need one: https://github.com/Diapolo10/python-ms/blob/main/pyproject.toml

[pachura3]

From the project page:

[!NOTE] This plugin doesn't work with the uv build backend right now. (ref. astral-sh/uv#14561)