You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would help simplify things if we set the internal version attribute to match what importlib.metadata for the package lists. That way, we don't need to keep repeating the version in a few places, and can leave it to the backend to properly manage.
In the past, I've had good success with versioneer to fetch version info from the git tag and reference that throughout the project. Does that seem like a workable solution for you?
I would like to avoid versioneer and any associated tools. They work well and were designed for use with setuptools, but don't fit the paradigms that build backends like CMake or meson-Python use
I think it would help simplify things if we set the internal version attribute to match what importlib.metadata for the package lists. That way, we don't need to keep repeating the version in a few places, and can leave it to the backend to properly manage.
For more information, see https://packaging.python.org/en/latest/discussions/single-source-version/#single-source-version
The text was updated successfully, but these errors were encountered: