On 2009-09-08, Chris Withers email@example.com wrote:
Sphinx, among others, provides command in this entry point.
With this buildout:
[buildout] parts = sphinx
[sphinx] recipe = zc.recipe.egg eggs = sphinx
And based on the entry points listed here:
I'd expect to be able to do:
$ bin/buildout setup setup.py build_sphinx
But I get:
Running setup script 'setup.py'. usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help
error: invalid command 'build_sphinx'
Yes: "bin/buildout setup setup.py something" tells buildout to run the "something" command with the setup.py in the current directory. And that won't be sphinx' setup.py.
Secondly: such an console_scripts entry point only tells setuptools (and buildout) to install that script in the bin directory. It is not an extra setup.py command (like "sdist" and "build"). For that, you need a different entry point.
When I just take your example buildout and run it, I get the expected result
$> bin/buildout Installing sphinx. Getting distribution for 'sphinx'. Got Sphinx 0.6.3. Generated script '/private/tmp/bbb/bin/sphinx-build'. Generated script '/private/tmp/bbb/bin/sphinx-quickstart'. Generated script '/private/tmp/bbb/bin/sphinx-autogen'.
So buildout installs the three defined console_scripts just fine in the bin/ directory.