You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using my own fork of sphinx_rtd_theme, but since the upstream version has already been installed by the time the project-specific requirements are installed, my fork is ignored because pip thinks that sphinx_rtd_theme is up-to-date.
This could be fixed by:
Keeping my fork's version higher than the upstream;
Giving it a different name;
Putting my fork directly in the project repository via e.g.git subtree;
Passing the --upgrade flag to the project-specific pip install.
(1) seems like a hack; (2) is also a hack; (3) is inelegant, since the theme already has a nice way of being required as a dependency, and subtrees are a pain anyway. So (4) seems like the best option, unless it would lead to problems on the RTD side.
Happy to submit a PR if this seems like a reasonable idea (pointing me to the relevant sections of the code would be helpful—I think it's readthedocs/doc_builder/python_environments.py?)
Details
I'm using my own fork of
sphinx_rtd_theme
, but since the upstream version has already been installed by the time the project-specific requirements are installed, my fork is ignored becausepip
thinks thatsphinx_rtd_theme
is up-to-date.This could be fixed by:
git subtree
;--upgrade
flag to the project-specificpip install
.(1) seems like a hack; (2) is also a hack; (3) is inelegant, since the theme already has a nice way of being required as a dependency, and subtrees are a pain anyway. So (4) seems like the best option, unless it would lead to problems on the RTD side.
Happy to submit a PR if this seems like a reasonable idea (pointing me to the relevant sections of the code would be helpful—I think it's
readthedocs/doc_builder/python_environments.py
?)The text was updated successfully, but these errors were encountered: