Dynamic Fashion Los Angeles

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

I've read through the dynamic metadata section of the docs. Hatch only accepts a path to store your version. When these fields are expected to be provided by.

Setting The Project Verion Dynamically Can Be Done By Changing Up The Following To Your Pyproject.toml.

3 dynamic versioning works differently on different build backends. See the dedicated versioning section. The name of the project.

Currently The Following Fields Can Be Listed As Dynamic:

To do this, you need to leave the version field out from your pyproject.toml and add version to the list of project.dynamic:

Hatch Only Accepts A Path To Store Your Version.

In such cases, you should mark the field as. For setuptools, there is an easier way to get. Judging by [tool.setuptools.dynamic], you're using setuptools.

The Name Of The Project.

3 dynamic versioning works differently on different build backends. Currently the following fields can be listed as dynamic: To do this, you need to leave the version field out from your pyproject.toml and add version to the list of project.dynamic:

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

See the dedicated versioning section. 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.

When These Fields Are Expected To Be Provided By.

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. Setting the project verion dynamically can be done by changing up the following to your pyproject.toml. If you need to reference it.

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