zhengruifeng commented on PR #44727:
URL: https://github.com/apache/spark/pull/44727#issuecomment-1891425213

   @wbo4958 It seems the `pydata_sphinx_theme` installations is not changed:
   it installs `pydata_sphinx_theme-0.15.1` in `Install Python linter 
dependencies`, and then `pydata_sphinx_theme-0.13.3` in `Install dependencies 
for documentation generation`, in both a successful run 
(https://github.com/apache/spark/actions/runs/7507799677/job/20442119109) and a 
failed one 
(https://github.com/apache/spark/actions/runs/7522706520/job/20475105206)
   
   The reason I think is `pydata_sphinx_theme` itself (both `0.15.1` and 
`0.13.3`) doesn't specify the versions of `sphinxcontrib-*`:
   ```
   │   ├── sphinxcontrib-applehelp               sphinxcontrib-applehelp is a 
Sphinx extension which outputs Apple help books
   │   ├── sphinxcontrib-devhelp                 sphinxcontrib-devhelp is a 
sphinx extension which outputs Devhelp documents
   │   ├── sphinxcontrib-htmlhelp>=2.0.0         sphinxcontrib-htmlhelp is a 
sphinx extension which renders HTML help files
   │   ├── sphinxcontrib-jsmath                  A sphinx extension which 
renders display math in HTML via JavaScript
   │   ├── sphinxcontrib-qthelp                  sphinxcontrib-qthelp is a 
sphinx extension which outputs QtHelp documents
   │   └── sphinxcontrib-serializinghtml>=1.1.9  sphinxcontrib-serializinghtml 
is a sphinx extension which outputs "serialized"
   ```
   
   then latest `sphinxcontrib-*` is not compatabile with sphinx.
   
   As to 3.5, I am not sure, since it uses `sphinx<3.1.0`, probably needs a 
separate fix
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to