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

stuck building documentation #3

Open
dlopezlo opened this issue Nov 20, 2019 · 9 comments
Open

stuck building documentation #3

dlopezlo opened this issue Nov 20, 2019 · 9 comments

Comments

@dlopezlo
Copy link

Hi,

environment created with versions below:

Sphinx==2.2.1
sphinx-prompt==1.1.0
sphinx-rtd-theme==0.4.3
sphinx-versions==1.1.3

the building gets always stuck like this:

=> Reading config from source/conf.py...
Running Sphinx v2.2.1
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 67 source files that are out of date
updating environment: [new config] 67 added, 0 changed, 0 removed
reading sources... [100%] index

looking for now-outdated files... none found
pickling environment... done 
checking consistency... done
preparing documents... done
writing output... [100%] index
generating indices...  genindexdone 
writing additional pages...  searchdone
copying images... [100%] Content/images/Installation/cmix_flavour_11.png
copying static files... ... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 1 warning.

The HTML pages are in ../../../../../../../var/folders/t_/kztj0hf94n30rxhf82blqv_c0000gn/T/tmphcz7mja3sphinxcontrib_versioning.

This happens with several sphinx-doc projects.

Note: The pending pull request is applied.

no more info if run with debug mode.

Any help or comment is very much appreciated.

@super-sk
Copy link

Hey it looks very similar to the bug on the original sphinxcontrib-versioning right here .

Unfortunately, it seems no PRs is merged ! :(

@paddy-hack
Copy link

Did you add sphinxcontrib.versioning.sphinx_ to the extensions array in your conf.py?

@fstompe
Copy link

fstompe commented Nov 29, 2019

I came across the same behaviour - in Python 3.6 - which is not yet officially supported. So the solution was to run it on Python 3.5.

@paddy-hack
Copy link

I'm using the above fix with Sphinx 2.2.1 on Debian 10's Python 3.7.3.

@super-sk
Copy link

@paddy-hack not tested yet. I also have to test workarounds from the original thread. ;)

@paddy-hack
Copy link

For this project's module you don't need the workarounds from the original thread .

@paddy-hack
Copy link

Forgot to mention, I actually use this project's module as I want to generate PDFs as well. This is something that the sphinxcontrib/versioning modules does support (yet?).

@Holzhaus
Copy link

It looks like the code to inject the extension into older branches is broken. I guess you have multiple branches/tags but only added the extension to conf.py on the latest (master) branch.

You can check this by restricting sphinx-version to master-only:

sphinx-versioning build -r master -w master -W this_tag_doesnt_exist <source> <build>

This works for me.

@paddy-hack
Copy link

A ugly fix was posted in sphinx-contrib/sphinxcontrib-versioning#70 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants