Closed DimitriPapadopoulos closed 1 year ago
Almost there, still an issue with docs, despite pinning down Jinja2:
ImportError: cannot import name 'environmentfilter' from 'jinja2'
Any clue? It looks like I am not updating Sphinx or pinning down Jinja2 the right way.
It seems that when doing the sphinx<4.0 install it installs jinja2 3.1.2
Collecting Jinja2>=2.3
Downloading Jinja2-3.1.2-py3-none-any.whl (133 kB)
It seems that when doing the sphinx<4.0 install it installs jinja2 3.1.2
in fact I don't know why it install sphinx < 4.0, this must be your question then :)
Any clue?
Probably CI broke at the time and this was a fix. It we can make it work with the latest sphinx version that would certainly be better.
Indeed the question is why it installs sphinx < 4.0. A quick grep comes up with:
setup.py Line 44 in c4faecf
'docs': ['sphinx>4.1.0', 'sphinx_rtd_theme', 'numpydoc', 'sphinx-click', 'jinja2<3.1.0']
doc/conf.py Line 28 in c4faecf
needs_sphinx = '4.1.0'
It looks like these have no effect at all, something else enforces sphinx<4.0
.
Here it asks for sphinx<4.0 in build_doc.sh
. This is what is called in CI.
Probably CI broke at the time and this was a fix. It we can make it work with the latest sphinx version that would certainly be better.
Yes, see #280
Base: 83.16% // Head: 80.83% // Decreases project coverage by -2.32%
:warning:
Coverage data is based on head (
759dded
) compared to base (4a8d2e5
). Patch coverage: 17.43% of modified lines in pull request are covered.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
I will keep sphinx<4.0
for now, and fix CI by pinning down jinja2<3.1.0
. Then we can address the upgrade of sphinx in a different merge request.
Note that tensoflow
and keras
are not pinned down any more. A single version for all version of Python doesn't seem to be working.
Ready for review.
thx @DimitriPapadopoulos