[Zope-dev] RFC: branch updating zc.buildout and bootstraps to use setuptools 0.7

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The bloody state of the winbot at the moment seems tied to issues related
to setuptools 0.6, distribute 0.5.4x, and zc.buildout.  I put in some
effort today on a branch to end-run the whole old-setuptools / distribute
bit by updating buildout2 to use the newly-availabe (but not yet released
to PyPI) setuptools 0.7.  This version is the first release after the
merge of old setuptools and distribute, and should be the preferred
target for future work.

My branch of buildout is here:

  https://github.com/tseaver/buildout/tree/use-setuptools-0.7

with a pull request to the main repo:

  https://github.com/buildout/buildout/pull/123

One issue that has to be worked around in the near term:  the 0.7 release
has been published via the bitbucket downloads page:

but not pushed to the cheeseshop.  I uploaded a hacked version of
'ez_setup.py' to deal with that interim problem here:

  http://dist.repoze.org/ez_setup-0.7.py

and my buildout branch uses that version.

I would like some help getting the manuel + renormalizer + doctest tests
working, or at least getting the "spurious" output differences smoothed
away so we can see real semantic changes, if any.

I'm assuming that it will take some days (weeks?) to get them passing, by
which point we can hope that the 0.7 release has been pushed to PyPI
(relieveing the need for a double-secret version of 'ez_setup.py').

Thoughts?


Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlGtQgUACgkQ+gerLs4ltQ59zwCeOScg3hciUGN3IyAltHfM0+eS
x/QAoMlUvQ5ifgiWnhuyQXqqdcP3Jjag
=BbxG
-----END PGP SIGNATURE-----