On Tue, Oct 6, 2009 at 2:16 PM, Guido van Rossum <gu...@python.org> wrote: > On Tue, Oct 6, 2009 at 11:03 AM, P.J. Eby <p...@telecommunity.com> wrote: >> At 02:45 PM 10/6/2009 +0100, Chris Withers wrote: >>>> >>>> To put this into a way that makes sense to me: I'm volunteering to keep >>>> distribute 0.6 and setuptools 0.6 in sync, no more, no less, and try and >>>> keep that as uncontroversial as possible, and get setuptools 0.6 releases >>>> out to match distribute 0.6 releases as soon as I can. >> >> That may not be as easy as it sounds; Distribute deleted various things from >> the setuptools tree (e.g. the release.sh script, used for issuing releases) >> and of course it adds other stuff (e.g. stuff to overwrite setuptools). So >> you'd need to screen the diffs. >> >> Second, I still intend to move setuptools 0.7 forward at some point, which >> means the patches also need to go to the trunk. > > Dream on. > >> If I had the time to co-ordinate and supervise all this, I'd have the time >> to just do it myself. > > I think at this point the community should not be forced wait for you > to get a new supply of round tuits. The wait has been too long > already. You can stay on in an advisory role, but I don't think it's > reasonable to block development or decisions until you have time. >
Is it possible to fork `setuptools` somehow ? This way : - patches may be built for setuptools 0.7 if it evolves - community can continue development in the «new» branch. all this easy if a DVCS is used ;o) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Nabble - Trac Users - Coupling trac and symfony framework - http://feedproxy.google.com/~r/TracGViz-full/~3/hlNmupEonF0/Coupling-trac-and-symfony-framework-td25431579.html _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
