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 have one issue that keeps creeping up. I noticed that sphinx-versioning copies the source code directory to a temporary directory, and then runs sphinx-build. Some projects do not exhibit a working run-time directory structure until setup.py is run and the components are built. In this case, if you copy the source directory, many local imports will fail. For example, my Python package has large C/C++ components with Python classes auto-generated in this process. A much more rudimentary example would be projects that use setuptools to generate a version.py that is then imported locally in __init__.py.
Can you offer an option to build each branch via setup.py? Something along the lines of:
Thanks for an awesome and very useful project!
I have one issue that keeps creeping up. I noticed that
sphinx-versioning
copies the source code directory to a temporary directory, and then runssphinx-build
. Some projects do not exhibit a working run-time directory structure untilsetup.py
is run and the components are built. In this case, if you copy the source directory, many local imports will fail. For example, my Python package has large C/C++ components with Python classes auto-generated in this process. A much more rudimentary example would be projects that usesetuptools
to generate aversion.py
that is then imported locally in__init__.py
.Can you offer an option to build each branch via
setup.py
? Something along the lines of:where
$prefixdir
is a temp prefix directory thatsphinx-versioning
runssphinx-build
against for each branch?Adding support for integration with
setuptools
will makesphinx-versioning
work out of the box with a wider variety of Python projects.The text was updated successfully, but these errors were encountered: