[Distutils] setuptools development cycle

[Tres Seaver]

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

Phillip J. Eby wrote:
> At 05:31 PM 10/4/2007 -0400, Tres Seaver wrote:
>> At this point, would we be better off moving aside the current trunk,
>> and making a new trunk from the 0.6 branch after getting 0.6 finally
>> released?
> 
> No way am I going to do the 2.5 work over again, so at least this 
> particular portion of "we" would not be better off.  :)

I was really trying to get an enumeration of the stuff done on that
branch which was not already backported.  For instance, there are a half
dozen or so 0.6 branch checkins which talk about backporting 2.5
compatibility fixes:  are there others not ported?

The real source of my worry is that anything which is on the trunk but
*not* on the 0.6 branch is potentially bitrotting, as nobody (AFAIK) is
actually using the trunk at this point.  Given that your itch is
currently scratched (I assume by 0.6?), I don't know who is able to help
maintain the trunk at all.

Here are the changelog messages from the trunk which I could not
identify as being ported (back or forward) to the 0.6 branch:

 - (r45403) Don't eagerly import namespace packages.

 - (r45405) Work toward inclusion in Python 2.5

 - (445514) Back/sideport a bunch of 2.5 modules (pkutil, pydoc,
   doctest) for use in 2.3 / 2.4.

 - (r45515,45517,45519,45521,45554) Python 2.5 compatibility changes

 - (r45719,45720) Added "internals" documentation

 - (r50538) Tweak docs for subversion release stuff to make better use
   of new options.

 - (r50536) Update aliases for easier release using new options

 - (r50562) Crosslink "Creating your own package index" to the new docs.

 - (r50921) Sync pkgutil from Python trunk

 - (r51931) Retain 2.3/2.4 compatibility as well...

 - (r51930) Python 2.5 compatibility fix

 - (r53309) Don't double-upload .exe files under Python 2.5.  :(

 - (r53645) Match Python 2.5 pydoc

 - (r54966) es Setting svn:eol properties everywhere where they weren't
   set yet.

I can't figure out from checkin comments (and a few diffs) exactly how
much of this stuff is "feature removal" (which your earlier message said
had been mostly done already), versus fixes to make it run under Python
2.5 (doesn't the 0.6 branch work fine under 2.5?), versus cleanups to
make the Python stdlib folks happy (or whatver).


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.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHBpT3+gerLs4ltQ4RAn44AKDaBqLrP9Pdx5DhMcDcASFywbNfPACfcjT1
7DmQZghfUqJnOzb9zx4UveE=
=bIDH
-----END PGP SIGNATURE-----