Distribute 0.7 development + 0.6 maint.
Hi, I've created a branch for the 0.6 maintenance. and the default is now for 0.7. 0.6 ---- The plan is to continue the bugfixes for the 0.6.x series there. If you want to work on this branch, you need to switch to it like this : $ hg update -C 0.6-maintenance (see http://mercurial.selenic.com/wiki/Branch) Then you can work with this wiki page here: http://bitbucket.org/tarek/distribute/wiki/bug_listing Basically, all issues from the setuptools tracker can be mirrored and fixed on our side, as long as it's a real bug fix (no API/behavior change) Patches are welcome ! 0.7 ---- The plan is to start the refactoring: - py3k support - split the code in several distributions - think about new features / behaviors, we need Help is welcome ! (of course we need to backport bugfixes from 0.6 to 0.7) Cheers Tarek -- Tarek Ziadé | http://ziade.org
On Sat, 08 Aug 2009 17:36:43 -0700, Tarek Ziadé
0.7 ---- The plan is to start the refactoring: - py3k support - split the code in several distributions - think about new features / behaviors, we need
And 0.7 will have different package namespace (thus not conflicting with an existing setuptools installation), correct? A while ago, PJE reported what he had in his mind regarding the package split. With that in mind, something like distribute.download, distribute.sandbox, distribute.metadata, distribute.installer, etc.. would be nice. PyPM already uses setuptools.package_index for downloading packages .. and might move to distribute if it provides a clean and separate API for doing this. -srid
participants (2)
-
Sridhar Ratnakumar
-
Tarek Ziadé