Automate document version to match plasmapy.__version__ #781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated definition of
release
andversion
indocs/conf.py
, so the documentation version will be automatically updated with the package versionplasmapy.__version__
.Note:
plasmapy.__version__
opposed to usingpkg_resources.get_distribution()
, because I want to rely on defining mechanics ofplasmapy.__version__
. By doing this, I also get a version number for the scenario where the package is notpip
installed.plasmapy.__version__
is not able to be generated, then it defaults to'unknown'
. However, theversion
attribute forSphinx
must follow a semantic versioning style, soversion = release = ''
is set ifplasmapy.__version__ == 'unknown'
.Closes #775