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

Sphinx build fails #116

Closed
florian-huber opened this issue Aug 11, 2020 · 9 comments · Fixed by #127
Closed

Sphinx build fails #116

florian-huber opened this issue Aug 11, 2020 · 9 comments · Fixed by #127

Comments

@florian-huber
Copy link
Collaborator

We suddenly get an documentation build error:
Extension error: Handler <function _process_docstring at 0x7fd1db87b0e0> for event 'autodoc-process-docstring' threw an exception (exception: module, class, method, function, traceback, frame, or code object was expected, got CPUDispatcher) Makefile:20: recipe for target 'coverage' failed make: *** [coverage] Error 2

@florian-huber
Copy link
Collaborator Author

Seems related to this: numpy/numpydoc#268 ?

@florian-huber
Copy link
Collaborator Author

florian-huber commented Aug 11, 2020

Seems to come from recent sphinx change from sphinx 3.1.2 to sphinx 3.2.0.

@florian-huber
Copy link
Collaborator Author

Fixed by setting sphinx<3.2.0 in PR #117 .
Should be checked again in some time to see if sphinx >3.2.0 would also work.

@sverhoeven
Copy link
Member

I think it is sphinx-doc/sphinx#8074

@florian-huber
Copy link
Collaborator Author

I am still a bit confused here: Why is the readthedocs build failing while the tests using sphinx 3.2.0 all pass?

@sverhoeven
Copy link
Member

I enabled harmonize_docstrings branch in https://readthedocs.org/projects/matchms/versions/, its build installs our conda/environent-dev.yml and then installs the latest sphinx with conda install --yes --quiet --name harmonize_docstrings mock pillow sphinx sphinx_rtd_theme which causes 3.2.0 to be installed.

@sverhoeven
Copy link
Member

Readthedocs build is green, as it is using Sphinx v3.2.1

@florian-huber
Copy link
Collaborator Author

Nice!
In principle we can close this now. Should we also change the version in environment-dev.yml, from sphinx>=3.0.0,<3.2.0 to sphinx>3.2.0 ?

@sverhoeven
Copy link
Member

Yes lets update conda env file. We could also use sphinx>=3.0.0,!=3.2.0,<4.0.0, so we keep the lowest version, but exclude the bad version (3.2.0) and dont get burned by a new incompatible major version.

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

Successfully merging a pull request may close this issue.

2 participants