Re: [Distutils] problem with http://nightly.ziade.org/distribute_setup.py
Tarek Ziadé wrote:
we have dropped the releases of egg format in 0.6.1 for various reasons,
Huh? Where are these reasons documented?
and the use_setuptools function cannot work anymore because it is exclusively using binary eggs and their ability to be used in sys.path as-is with zero installation.
So much for drop-in compatibility with setuptools :-(
Florian Schulze and I started another repo to create a new bootstrap.py that will bootstrap a zc.buildout environment using Distribute.
How about working on the buildout branch I'm working on rather than doing stuff separately all the time? Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Thu, Sep 10, 2009 at 3:05 PM, Chris Withers
Tarek Ziadé wrote:
we have dropped the releases of egg format in 0.6.1 for various reasons,
Huh? Where are these reasons documented?
Because besides zc.buildout bootstraping, the distribute_setup.py is not be considered as part of the code API.
and the use_setuptools function cannot work anymore because it is exclusively using binary eggs and their ability to be used in sys.path as-is with zero installation.
So much for drop-in compatibility with setuptools :-(
This is not a compatibility issue. The code stays unchanged. This is just a change in the way we release this project: no more binary releases in bdist_egg format that is. Just a plain source release. The ability to create an egg still exists, nothing has changed.
Florian Schulze and I started another repo to create a new bootstrap.py that will bootstrap a zc.buildout environment using Distribute.
How about working on the buildout branch I'm working on rather than doing stuff separately all the time?
Because it's not the zc.buildout project. It's a project that creates a zc.buildout environment using distribute, like what virtualenv-distribute does with virtualenv. n.b. : Please, when you send a private mail, do not send the replies in the mailing list like that. It's confusing for people that try to follow the threads. The best way is to send all your requests to distutils-SIG, thx. Tarek -- Tarek Ziadé | http://ziade.org | オープンソースの岩!
Tarek Ziadé wrote:
On Thu, Sep 10, 2009 at 3:05 PM, Chris Withers
wrote: Tarek Ziadé wrote:
we have dropped the releases of egg format in 0.6.1 for various reasons, Huh? Where are these reasons documented?
Because besides zc.buildout bootstraping, the distribute_setup.py is not be considered as part of the code API.
What does that have to do with egg format releases of the 0.6 branch?
This is not a compatibility issue. The code stays unchanged. This is just a change in the way we release this project: no more binary releases in bdist_egg format that is. Just a plain source release.
Setuptools is available as an egg, so if you want 100% backwards compatability, then distribute needs to be too...
http://bitbucket.org/tarek/buildout-distribute/ How about working on the buildout branch I'm working on rather than doing stuff separately all the time?
Because it's not the zc.buildout project. It's a project that creates a zc.buildout environment using distribute, like what virtualenv-distribute does with virtualenv.
*sigh* How many forks of how many projects do you want? Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Thu, Sep 10, 2009 at 3:17 PM, Chris Withers
Because it's not the zc.buildout project. It's a project that creates a zc.buildout environment using distribute, like what virtualenv-distribute does with virtualenv.
*sigh*
How many forks of how many projects do you want?
I am not forking anything. I don't plan to integrate Distribute in zc.buildout right now. As Jim said, and as I repeated, the only thing that could be possibly done in zc.buildout is to make it compatible with any pre-requested distribution (distribute/setuptools/etc). I am just going to provide a script to make it easier for people to set up distribute in a zc.buildout project. That's just a bootstrap script....
Tarek Ziadé wrote:
How many forks of how many projects do you want?
I am not forking anything. I don't plan to integrate Distribute in zc.buildout right now.
Right, so people have to use a special bootstrap.py to get distribute? That bootstrap.py will diverge from the one in buildout at some point causing problems.
As Jim said, and as I repeated, the only thing that could be possibly done in zc.buildout is to make it compatible with any pre-requested distribution (distribute/setuptools/etc).
Huh? The branch I have is all but complete... Well, it was until you pulled the rug out from underneath me by not sticking to the backwards compatibility you promised... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Thu, Sep 10, 2009 at 3:29 PM, Chris Withers
Tarek Ziadé wrote:
How many forks of how many projects do you want?
I am not forking anything. I don't plan to integrate Distribute in zc.buildout right now.
Right, so people have to use a special bootstrap.py to get distribute? That bootstrap.py will diverge from the one in buildout at some point causing problems.
What problem ? If you want a zc.buildout with Distribute, install Distribute after your regular bootstrap and you have it.
As Jim said, and as I repeated, the only thing that could be possibly done in zc.buildout is to make it compatible with any pre-requested distribution (distribute/setuptools/etc).
Huh? The branch I have is all but complete... Well, it was until you pulled the rug out from underneath me by not sticking to the backwards compatibility you promised...
Sure, I made an error by changing this script like that. I am going to reintroduce this function so you can run it. You can use the 0.6 script until 0.6.3 is out.
Chris
-- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
-- Tarek Ziadé | http://ziade.org | オープンソースの岩!
participants (2)
-
Chris Withers
-
Tarek Ziadé