Tarek Ziadé wrote:
On Thu, Aug 6, 2009 at 4:29 PM, Chris Withers<[email protected]> wrote:
for the scripts created in zc.recipe.egg sections, so distribute is
included in the sys.path
since this recipe re-creates it.
Am I right in thinking this wouldn't be needed if zc.buildout and
zc.recipe.egg both depended on distribute rather than setuptools?
Yes, but I think this takes more energy and more time to convince Jim, then
work in zc.buildout
It really doesn't look like a lot of work, in fact I knocked up a branch
that shows just that:
http://svn.zope.org/zc.buildout/branches/use_distribute/
The changeset required was actually pretty small:
http://zope3.pov.lt/trac/changeset/102544
When a distribute egg gets released, I'll try running these tests and
see what happens...
If we take the plone example, every single egg has it (because it's in
the zopeskel skeleton)
*sigh* Plone suck strikes again :-(
I'd rather be able to run already released eggs in my buildout today
rather than waiting for
the crowd to adopt it.
Plus, people wont adopt it if they can't taste it,
I guess that's the way it needs to be, and all for the stubbornness of
Phil Eby...
bootstraping.py replaces ez_setup.py
Oh Tarek, you really do know how to pick names...
Any chance you could switch this to distribute_setup.py or maybe d_setup.py
to avoid dumb people like me constantly confusing the two?
Sure. distribute_setup.py sounds good, I can change. That will be the
name, no further
change :)
Thanks.
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
