Greg Stein writes:
Or in the "network" package that was suggested a month ago?
[Fred]
+1
Which reminds me of another reason to wait: coming up with the right package hierarchy is hard. (E.g. I find network too long; plus, does htmllib belong there?)
That doesn't bother me, but I tend to be a little conservative (though usually not as conservative as Guido on such matters). I *would* like to decided theat 1.7 will be fully packagized, and not wait until 2.0. As long as 1.7 is a "testing the evolutionary path" release, I think that's the right thing to do.
Agreed. At the SD conference I gave a talk about the future of Python, and there was (again) a good suggestion about forwards compatibility. Starting with 1.7 (if not sooner), several Python 3000 features that necessarily have to be incompatible (like 1/2 yielding 0.5 instead of 0) could issue warnings when (or unless?) Python is invoked with a compatibility flag. --Guido van Rossum (home page: http://www.python.org/~guido/)