-
Notifications
You must be signed in to change notification settings - Fork 33
Description
When I worked in #821, I noticed that sphinx-autobuild would go into infinite loop after a first change is done by the user. I looked into reported issues for sphinx-autobuild and found sphinx-doc/sphinx-autobuild#187. I experimented with a few minimal working examples, see sphinx-doc/sphinx-autobuild#187 (comment), and with some changes in this team-compass repository and my conclusion is that
Lines 64 to 67 in 47543e3
| from subprocess import run | |
| run(["python", "_data/contributors/gen_contributors.py"], check=True) | |
| run(["python", "_data/outreachy/outreachy_participants.py"], check=True) |
sphinx-autobuild. I don't remember where I read that add file creation in conf.py is a anti-pattern and, instead, people should create their own Sphinx extension.
The cross road here is that instructions in conf.py make it easy to contributors to find it but it make "impossible" for contributors to use sphinx-autobuild. IMHO, contributions to the documentation should be the low hanging fruit of a project and new contributors should have a good experience. My recommendation is to refactor https://github.com/jupyterhub/team-compass/blob/47543e390dc162502ab3c2150481c2607bca919f/docs/_data/contributors/gen_contributors.py and https://github.com/jupyterhub/team-compass/blob/47543e390dc162502ab3c2150481c2607bca919f/docs/_data/outreachy/outreachy_participants.py into a Sphinx extension to allow contributors to use sphinx-autobuild.
I'm interested to hear the thoughts of others.