On Jan 3, 2008 12:17 PM, Bill Janssen <[EMAIL PROTECTED]> wrote: > > My main gripe is with code contributions to Py3k and 2.6; Py3k is > > mostly done by a handful of people, and almost nobody is working much > > on 2.6. > > There's a great Duke Ellington quote: ``Without a deadline, baby, I > wouldn't do nothing.'' > > The SSL code in 2.6 is out-of-date (buggy) compared to the code in the > 3.x branch, for instance. I just haven't prioritized backporting the > 3.x fixes, because there's no schedule for 2.6.
Eh? PEP 3000 has a schedule that includes 2.6: * August 2007: release 3.0a1. * December 2007: release 3.0a2. * Early 2007 (pre-PyCon): release 2.6a1. * May 2008 (post-PyCon): full feature freeze for 3.0 and 2.6. * July 2008: release 2.6 (final). * August 2008: release 3.0 (final). -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ 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
