Derive project version in docs from Git Tags

[seifertm]

The project version specified in docs/source/conf.py has not been bumped since v0.20.1.

The release field should be derived automatically from the version determined by setuptools_scm, so there's no need to adjust the version manually upon creating a release.

[marcolab]

Hi! I would like to work on this issue

[seifertm]

Great! Let me know if you encounter any issues or if you need a few pointers.

[marcolab]

I was thinking of simply doing the same as is done in tools/get-version.py. So using importlib.metadata to derive the version in docs/source/conf.py. Would that work?

[seifertm]

That sounds like a reasonable approach.

I noticed it's possible for the venv to contain an outdated version of pytest-asyncio. This may lead to outdated values for release, if we go with this approach. However, I think that this problem needs to be handled separately from this issue.

Your approach is the way to go in my opinion.

[menkotoglou]

Hey @marcolab, did you have the time to look into it? Maybe need a helping hand?

[ka28kumar]

Hello @seifertm,
We can get the version either using importlib.metadata.version("pytest-asyncio") or setuptools_scm.get_version(). Which one would you prefer?

[seifertm]

@ka28kumar I'd prefer the use of importlib.metadata, because it is part of the standard library in recent versions of Python.