Skip to content

Report version number to Sphinx#60

Closed
minchinweb wants to merge 1 commit into
bitprophet:masterfrom
minchinweb:report-version
Closed

Report version number to Sphinx#60
minchinweb wants to merge 1 commit into
bitprophet:masterfrom
minchinweb:report-version

Conversation

@minchinweb

Copy link
Copy Markdown
Contributor

In particular, the version number will show up in the Sphinx log. So instead of:

# Sphinx version: 1.3
[...]
# Loaded extensions:
#   alabaster (0.7.9) from c:\tmp\releases-multiple\env\lib\site-packages\alabaster\__init__.py
#   releases (unknown version) from c:\tmp\releases-multiple\env\lib\site-packages\releases\__init__.py
[...]

you get:

# Sphinx version: 1.3
[...]
# Loaded extensions:
#   alabaster (0.7.9) from c:\tmp\releases-multiple\env\lib\site-packages\alabaster\__init__.py
#   releases (1.2.1) from c:\tmp\releases-multiple\env\lib\site-packages\releases\__init__.py
[...]

@bitprophet

Copy link
Copy Markdown
Owner

Thanks! Would you believe I've been working with Sphinx and sphinx extensions for years and had no idea this was a thing? 🙃

@bitprophet bitprophet added the bug label Sep 9, 2016
@bitprophet bitprophet modified the milestones: 1.3, 1.2.2 Sep 9, 2016
@minchinweb

Copy link
Copy Markdown
Contributor Author

It makes you wonder what other little, but useful, features are hiding just under the surface...

@bitprophet

bitprophet commented May 18, 2017

Copy link
Copy Markdown
Owner

Hilariously, now that I revisit this I see somebody must have introduced me to this Sphinx feature in passing beforehand, because...it's in Alabaster too... 🙃

@minchinweb minchinweb deleted the report-version branch May 19, 2017 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants