Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report version number to Sphinx #60

Closed
wants to merge 1 commit into from

Conversation

MinchinWeb
Copy link
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
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
Contributor Author

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

@bitprophet
Copy link
Owner

bitprophet commented May 18, 2017

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.

None yet

2 participants