-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 13.01.2011 09:12, schrieb Jason: > On Jan 13, 3:33 pm, Georg Brandl <ge...@python.org> wrote: >> > Is there any way around this? >> >> Yes: build the C extension before you build the docs. > > I use distutils to build it all, which deposits everything in a > variably named build/lib.linux-ARCH-PYVERSION dir. I've searched the > Sphinx docs for info on distutils integration, and the distutils docs > for Sphinx integration, but with no luck. > > Do you have any pointers on how I can get distutils to invoke the > Sphinx builder with the right sys.path settings every time?
Sphinx does include a "setup.py build_docs" command, but it does not handling adding the distutils build directories to sys.path. It would probably a good idea to do this -- would you like to work on a patch? What I usually do is to copy the built C modules to the source path in my "make the docs" step: cp build/lib.*/_module.so src/package cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0xZQUACgkQN9GcIYhpnLDupwCfd6bvaiaIkNEqjSAHcUJ41J8R KOgAnRL65preAFeAI6Evw1K+mCZT2sIt =sB6c -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
