Once a 0.6 release is made and we get a maintenance branch for it, we should look into the changes made on setuptools trunk and apply them again.
I reviewed all the changesets made since the original 0.6 branch was created and found the following changesets which were unique to the trunk.
It seems to be three changes:
- A new test_runner option
- Integration / cleanup work done when Python 2.5 can be required
- Lazy importing of namespace packages
I consider all of these safe to do, though the Python 2.5 changes may need another review or tweaks now.
The full revision log is:
r65966 | phillip.eby | 2008-08-21 23:54:16 +0200 (Thu, 21 Aug 2008) | 3 lines
Added 'test_runner'. (Note: this is a new feature and should not
be backported to the 0.6 branch.)
r50921 | phillip.eby | 2006-07-29 01:58:14 +0200 (Sat, 29 Jul 2006) | 2 lines
Sync pkgutil from trunk
r45514 | phillip.eby | 2006-04-18 05:03:16 +0200 (Tue, 18 Apr 2006) | 9 lines
Backport pkgutil, pydoc, and doctest from the 2.5 trunk to setuptools
0.7 trunk. (Sideport?) Setuptools 0.7 will install these in place of
the 2.3/2.4 versions (at least of pydoc and doctest) to let them work
properly with eggs. pkg_resources now depends on the 2.5 pkgutil, which
is included here as _pkgutil, to work around the fact that some system
packagers will install setuptools without overriding the stdlib modules.
But users who install their own setuptools will get them, and the system
packaged people probably don't need them.
r45405 | phillip.eby | 2006-04-14 21:38:38 +0200 (Fri, 14 Apr 2006) | 4 lines
First round of prepping setuptools for inclusion in Python 2.5: move
site.py to setuptools/site-patch.py; reinstate 'python -m easy_install'
support; use distutils' "upload" command when running under 2.5.
r45404 | phillip.eby | 2006-04-14 21:17:37 +0200 (Fri, 14 Apr 2006) | 2 lines
Namespace package doc tweaks.
r45403 | phillip.eby | 2006-04-14 21:13:24 +0200 (Fri, 14 Apr 2006) | 4 lines
Don't eagerly import namespace packages. This was the big reason for
branching to 0.7 now, as I wanted this wart gone before anything went
into Python 2.5. But it's gone now, yay!