Dynamic Fashion Poses

When These Fields Are Expected To Be Provided By.

Judging by [tool.setuptools.dynamic], you're using setuptools. I've read through the dynamic metadata section of the docs. See the dedicated versioning section.

Then Use Importlib.metadata.version To Get The Version Number.

The name of the project. Setting the project verion dynamically can be done by changing up the following to your pyproject.toml. Hatch only accepts a path to store your version.

To Do This, You Need To Leave The Version Field Out From Your Pyproject.toml And Add Version To The List Of Project.dynamic:

In such cases, you should mark the field as.

In Such Cases, You Should Mark The Field As.

Hatch only accepts a path to store your version. See the dedicated versioning section. Setting the project verion dynamically can be done by changing up the following to your pyproject.toml.

I've Read Through The Dynamic Metadata Section Of The Docs.

For setuptools, there is an easier way to get. Then use importlib.metadata.version to get the version number. The name of the project.

However, If You Want The Version To Be Available In The Variable __Version__ In The __Init__.Py File Of Your Module, You Need To Dynamically Update The Value Of This Variable When.

Currently the following fields can be listed as dynamic: Many build backends can read the version from a __version__ attribute in your code, a git tag, or similar. Project metadata is stored in a pyproject.toml file located at the root of a project's tree and is based entirely on the standard.

Judging By [Tool.setuptools.dynamic], You're Using Setuptools.

If you need to reference it. When these fields are expected to be provided by. To do this, you need to leave the version field out from your pyproject.toml and add version to the list of project.dynamic:

3 Dynamic Versioning Works Differently On Different Build Backends.