Closed kloczek closed 2 years ago
I forgot to mention that to use straight sphinx-build
commend is necessatchy to use patch like below:
--- a/docs/conf.py~ 2022-03-17 09:29:00.000000000 +0000
+++ b/docs/conf.py 2022-06-15 16:44:10.255216368 +0000
@@ -16,16 +16,15 @@
import sys
import os
-import pkg_resources
-import datetime
-
# If your extensions are in another directory, add it here. If the directory
# is relative to the documentation root, use os.path.abspath to make it
# absolute, like shown here.
sys.path.insert(0, os.path.abspath('.'))
-sys.path.insert(0, os.path.abspath(".."))
+sys.path.insert(0, os.path.abspath("../src"))
+import pkg_resources
+import datetime
# General configuration
# ---------------------
Also ZODB
uses pkg_resources
so it would be good to migtate to importlib-metadata
https://github.com/pypa/setuptools/issues/3279
Call trace poited on j1m-sphinxautozconfig
(this module seems is not maintained since 2016) however after remove that module
--- a/docs/conf.py~ 2022-06-15 18:44:34.000000000 +0000
+++ b/docs/conf.py 2022-06-15 18:48:40.761196441 +0000
@@ -39,7 +39,6 @@
'sphinx.ext.intersphinx',
'sphinx.ext.viewcode',
'sphinxcontrib.zopeext.autointerface',
- 'j1m.sphinxautozconfig',
]
# Add any paths that contain templates here, relative to this directory.
sphinx still fails
This time call trace points on sphinxcontrib.zopeext.autointerface
.
Maybe it would b better switch to regular repoze-sphinx-autointerface
or reguler sphinx-autoapi
? 🤔
Fedora has upgraded to sphinx 5.x in Rawhide, so the ZODB package is currently failing during the documentation building step. We would love to see a fix for this issue so that we can keep building the documentation.
Fedora has upgraded to sphinx 5.x in Rawhide, so the ZODB package is currently failing during the documentation building step. We would love to see a fix for this issue so that we can keep building the documentation.
Fedora is producing html so my patch may be not enough for you (remove failing extension has no significant impact in case of roff output). Nevertheless this issue is related to usefailing sphinx extension.
The way to build the documentation for this project is to call:
tox -edocs
This runs successfully as shown by GitHub Actions. There are no guaranties that it is successful in any other way.
It currently uses Sphinx v4.5.0. The reason behind is that the sphinxcontrib-zopeext
does not yet support Sphinx 5.x, see https://github.com/sphinx-contrib/zopeext/blob/b749d0023f4fb8b8eea3a8f3216f63397c6272de/pyproject.toml#L17
See https://github.com/sphinx-contrib/zopeext/issues/7 as the issue which has to be solved beforehand.
Your tox target generates html. I need roff output (man page). Did you try to generated man page before writing that I should use tox?
@kloczek Thank you for the clarification what you need and what you want to achieve. It was not clear to me from the previous entries, sorry.
My comment about tox
is still valid though: It installs the dependencies in the correct versions. We could change the tox configuration file, so you could add additional parameters to the sphinx-build
call via the tox call on the command line to create the output format you need. – Would this help you?
@kloczek Thank you for the clarification what you need and what you want to achieve. It was not clear to me from the previous entries, sorry.
First line of the log had command which I've been running 😋
+ /usr/bin/sphinx-build -n -T -b man docs build/sphinx/man
My comment about tox is still valid though: It installs the dependencies in the correct versions
Really .. please have look one more time on the log whis aI've added to the ticket. None in that output pooints on missing bits in build env.
Here is list of modules installed in build env
Tomasz Kłoczko wrote at 2022-8-31 04:35 -0700:
... Really .. please have look one more time on the log whis aI've added to the ticket.
... Package Version
... Sphinx 5.1.1 ...
You have been told (--> "https://github.com/zopefoundation/ZODB/issues/363#issuecomment-1232520739") that the documentation build currently cannot use Sphinx 5.x (together with good reasons).
(--> "#363 (comment)") that the documentation build currently cannot use Sphinx 5.x (together with good reasons).
I want only to dsay that maybe it is time to choose other sphinx extension which is conuosly updated for sphinx 5.x? Sphinx no longer maintains 4.x 🤔 (and there isa no any plans to continue 4.x maintainance https://github.com/sphinx-doc/sphinx/branches)
@kloczek Thank you for sharing your environment. I don't know how you got there but it is invalid: sphinxcontrib-zopeext == 0.3.2
defines in its dependencies that it requires Sphinx = ">=3.4.2,<5.0.0"
, so pip
should prevent installing it together with Sphinx >= 5
.
Thank you for the hint to think about better dependencies. We'll postpone it until having an actual problem with Sphinx 4 due to limited time and manpower.
I am closing this issue as invalid
as there is no actual error building the docs when using the expected tools. Feel free to open a new issue if you want to use tox
to build the man-page format.
Looks like it is not possible to generate documentation using sphinx 5.x