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
Updates for tox and sphinx #157
Conversation
Sphinx 6.1 deprecates
edit: it is raised in our tests where we run sphinx with |
What is the future of automodapi ? Is it time we retire it in favor of something else that the wider ecosystem uses? If so, then maybe it is ok to ignore the warning. |
Where is progress_message even called? I cannot find it here. If it is not our problem, let's ignore. |
There is https://github.com/readthedocs/sphinx-autoapi but I don't know how it compares to automodapi |
I don't remember exactly but it's called in some Sphinx extension I think. The problem is that in our tests we are calling sphinx-build with sphinx-automodapi/sphinx_automodapi/tests/test_cases.py Lines 134 to 140 in 6e476f2
|
I ignored that warning in |
Might have to put that |
Codecov Report
@@ Coverage Diff @@
## main #157 +/- ##
=======================================
Coverage 89.90% 89.90%
=======================================
Files 27 27
Lines 1139 1139
=======================================
Hits 1024 1024
Misses 115 115 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Now the Windows job failed... |
The warning ignores in setup.cfg are for pytest, not sphinx. |
LoL I cannot keep up. Doesn't explain the Windows failure though. |
@saimn , does this mean we can remove the changes to |
We don't do backports here, so I am just gonna "squash and merge" when CI passes. Thanks! |
homebrew complained about the |
Thanks, @saimn ! |
While trying to make a release I found a few issues with recent version of tox and sphinx ...