On Sep 27, 2007, at 8:00 AM, Philipp von Weitershausen wrote:
...
buildout setup? I've never seen that. I can't find any
documentation on it in zc.buildout.
Grrrr. Sure enough, the documentation doesn't mention it. That's an
annoying documentation bug, I'm pretty sure it was documented at one
time. Also, some examples in the documentation use it.
How does it work?
bin/buildout setup <somedir_or_setup_script> setup arguments ...
Does it call setup.py for every development egg in buildout.cfg?
No.
Why not just call python setup.py?
Because:
- The setup you are invoking uses setuptools and you are using a
clean Python, or
- The the setup.py you're using doesn't use setuptools but you want
to use setuptools commands.
Basically, the setup command is a convenience that gets setuptools
into the path and imported before invoking the given setup. I find
this quite useful. One annoyance is that, although there are
workarounds, it generally wants there to be a buildout.cfg file
around and I often want to use it to run a setup.py that has nothing
to do with a buildout.
Jim
--
Jim Fulton
Zope Corporation
_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com