-
Notifications
You must be signed in to change notification settings - Fork 8
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
Sphinx docs version #103
Comments
I would be fine with it keeping the same number as the current Taweret version. I will fix this before the v0.4 release. |
I attempted the fix above, but it failed. Will figure out how to fix that, since I think we have the version set up in the |
Make sure that you import |
I think it's working now. |
OK now it is building with the simpler |
Look good, closing. |
The PDF version of the sphinx docs list the document as release 0.1.0, which I suspect is taken from the sphinx file
conf.py
. Do you want the version of the doc to have its own version number or be tied to the version of the Taweret python package? For the latter, you should be able to setup the package (if not already done so) so that after importing Taweret inconf.py
you can get the package's version number from the package itself (e.g.,release = Tawaret.__version__
).The text was updated successfully, but these errors were encountered: