pydata / pydata/patsy

0.5.3: documentation build fails with sphinx 6.2.1

Open
#193 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Python
Stars
990
Forks
106
Avg merge
7d 34m
Merged PRs (30d)
1

Description

Looks like doc/content needs to be updated for sphinx +6.x

+ /usr/bin/sphinx-build -n -T -b man doc build/sphinx/man
Running Sphinx v6.2.1
python exec: /usr/bin/python3
sys.path: ['/usr/bin', '/usr/lib64/python38.zip', '/usr/lib64/python3.8', '/usr/lib64/python3.8/lib-dynload', '/home/tkloczko/.local/lib/python3.8/site-packages', '/usr/lib64/python3.8/site-packages', '/usr/lib/python3.8/site-packages']
numpy: 1.24.3, /usr/lib64/python3.8/site-packages/numpy/__init__.py
matplotlib: 3.6.3, /usr/lib64/python3.8/site-packages/matplotlib/__init__.py
ipython: 8.12.0, /usr/lib/python3.8/site-packages/IPython/__init__.py
making output directory... done

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/sphinx/cmd/build.py", line 280, in build_main
    app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/usr/lib/python3.8/site-packages/sphinx/application.py", line 243, in __init__
    self.config.setup(self)
  File "/home/tkloczko/rpmbuild/BUILD/patsy-0.5.3/doc/conf.py", line 70, in setup
    app.add_javascript("show-code.js")
AttributeError: 'Sphinx' object has no attribute 'add_javascript'

Exception occurred:
  File "/home/tkloczko/rpmbuild/BUILD/patsy-0.5.3/doc/conf.py", line 70, in setup
    app.add_javascript("show-code.js")
AttributeError: 'Sphinx' object has no attribute 'add_javascript'
The full traceback has been saved in /tmp/sphinx-err-8x1irlvx.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the documented sphinx-build command and inspect doc/conf.py, especially setup at line 70 where the Sphinx 6.2.1 build fails. Review the surrounding documentation configuration and doc content for the compatibility issue. Done means the documentation build completes successfully with Sphinx 6.2.1.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.