Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fix documentation build for Python 3

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with docs/source/conf.py, especially the execfile call shown in the traceback, and run make html under Python 3 to identify any additional configuration failures. Done means the documentation build completes successfully under Python 3.

Written by the indexing model from the issue text.

Description

The documentation doesn't currently build under Python 3. The immediate error is due to use of execfile in the Sphinx configuration, but there may be others.

mirzakhani:docs mdickinson$ make html
sphinx-build -b html -d build/doctrees   source build/html
Running Sphinx v1.8.3

Configuration error:
There is a programmable error in your configuration file:

Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/sphinx/config.py", line 368, in eval_config_file
    execfile_(filename, namespace)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
    exec_(code, _globals)
  File "/Users/mdickinson/Enthought/ETS/codetools/docs/source/conf.py", line 44, in <module>
    execfile(os.path.join('..', '..', 'codetools', '__init__.py'), d)
NameError: name 'execfile' is not defined

make: *** [html] Error 2
Dominant language
Python
Stars
54
Forks
10
PR merge metrics
No merged PRs in 30d

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.

More from enthought/codetools

All issues in enthought/codetools

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.