Regarding sort()

Scott David Daniels Scott.Daniels at Acm.Org
Tue May 26 09:35:51 EDT 2009

Jaime Fernandez del Rio wrote:
>... the reasons are starting to pile to fare 2.6 goodbye and move on to 3.0...
If you wait just a bit (TM)*, you'd be better served to move on to
3.1.  I think 3.0 is for learning, both for Python developers and
users, and has less "fit and polish" than previous Python releases.
Between 2.x and 3.0, there were huge changes, and some substantial
restructuring.  The move to Unicode strings was not without its
bumps and bruises, and efficiency was (quite properly) by no means
the top priority.  As a result, "normal" file I/O on 3.0 is slowed,
and getting that fixed was not a priority (as correctness was plenty
of work).

I'd view 3.0 as the first real-world view of Python 3000, and 3.1 as
getting the surprise burs and sharp edges of 3.0 cleaned up a bit.

* 3.1 is already in beta, according to PEP 375, the first release
   candidate is coming 30-May, with final release on 27-June:

--Scott David Daniels
Scott.Daniels at Acm.Org

More information about the Python-list mailing list