Closed jjacob7734 closed 8 months ago
Hi @jjacob7734, to quickly get some docs built, try:
sphinx-build docs/source docs/build
open docs/build/index.html
However, the real problem is that it looks like Sphinx is not installing a setup.py
extension command to build the docs. This is because in your setup.cfg
you have sphinx
listed without a version pin, which means "grab me the latest".
The Python template repo uses sphinx~=3.2.1
. If I add that to your setup.cfg
, then I get python setup.py build_sphinx
—but it fails because the Jinja2 dependency is also too high. If I also add Jinja2<3.1
, then python setup.py build_sphinx
works fine.
In fact, you'll probably want to pin all your dev dependencies in order to avoid the version confusion security vulnerability. Here are the correct pins to use from the Python template repo:
black~=23.7.0
flake8~=6.1.0
flake8-bugbear~=23.7.10
flake8-docstrings~=1.7.0
pep8-naming~=0.13.3
mypy~=1.5.1
pydocstyle~=6.3.0
coverage~=7.3.0
pytest~=7.4.0
pytest-cov~=4.1.0
pytest-watch~=4.2.0
pytest-xdist~=3.3.1
pre-commit~=3.3.3
sphinx~=3.2.1
sphinx-rtd-theme~=0.5.0
tox~=4.11.0
types-setuptools~=68.1.0.0
Jinja2<3.1
@nutjob4life committed the fix for this to the sinequa-api-notebook
branch to be merged.
Hi @jjacob7734, to quickly get some docs built, try:
sphinx-build docs/source docs/build open docs/build/index.html
However, the real problem is that it looks like Sphinx is not installing a
setup.py
extension command to build the docs. This is because in yoursetup.cfg
you havesphinx
listed without a version pin, which means "grab me the latest".The Python template repo uses
sphinx~=3.2.1
. If I add that to yoursetup.cfg
, then I getpython setup.py build_sphinx
—but it fails because the Jinja2 dependency is also too high. If I also addJinja2<3.1
, thenpython setup.py build_sphinx
works fine.In fact, you'll probably want to pin all your dev dependencies in order to avoid the version confusion security vulnerability. Here are the correct pins to use from the Python template repo:
black~=23.7.0 flake8~=6.1.0 flake8-bugbear~=23.7.10 flake8-docstrings~=1.7.0 pep8-naming~=0.13.3 mypy~=1.5.1 pydocstyle~=6.3.0 coverage~=7.3.0 pytest~=7.4.0 pytest-cov~=4.1.0 pytest-watch~=4.2.0 pytest-xdist~=3.3.1 pre-commit~=3.3.3 sphinx~=3.2.1 sphinx-rtd-theme~=0.5.0 tox~=4.11.0 types-setuptools~=68.1.0.0 Jinja2<3.1
Checked for duplicates
Yes - I've already checked
🐛 Describe the bug
When I commit to my own branch (
sinequa-api-notebook
) in theplanetary-data-engine
repo the automated CI/CD workflow gets the following error:error: invalid command 'build_sphinx'
. The relevant lines in the log are:🕵️ Expected behavior
I expected the commit to have no errors. This error is in a part of the repo that I don't touch.
📜 To Reproduce
Run failed: Branch integraion testing
🖥 Environment Info
📚 Version of Software Used
🩺 Test Data / Additional context
No response
🦄 Related requirements
No response
⚙️ Engineering Details
No response