sphinx-build path in Makefile does not respect virtualenv

Anonymous avatarAnonymous created an issue

If I use virtualenv to run sphinx-quickstart from a particular virtual environment, it seems reasonable to expect that I'd also like to run the sphinx-build from that same environment. However, the generated Makefile currently just contains the vanilla

SPHINXBUILD   = sphinx-build

which runs the systemwide sphinx-build. For example, if I run

$ virtualenv ~/py26
$ ~/py26/bin/easy_install sphinx
$ ~/py26/bin/sphinx-quickstart

I would expect the generated Makefile to contain

SPHINXBUILD   = ~/py26/bin/sphinx-build

This could probably be fixed by prepending the path of the running sphinx-quickstart to the generated sphinx-build command in the Makefile.

Comments (4)

  1. Georg Brandl

    I don't think this is a good idea. The default path in the Makefile should not depend on details of your system; it should be general enough that the Makefile works when you distribute the documentation to others. An exception is when you're using a customized sphinx-build that lives somewhere in the distributed tree. Also, isn't the usual usage of virtualenv that you activate the env before doing anything in it?

    Summarily, you can still set it by hand, of course, but I won't change the default.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.