Main Content

Python 3000 - the next generation

Archive - Originally posted on "The Horse's Mouth" - 2006-06-09 05:56:00 - Graham Ellis

There is no definite schedule for Python 3 (a.k.a. Python 3000 or Py3K) but a Python Enhancement Proposal (PEP) that details plans exists. There's a guiding principle to reduce duplication by removing old ways of doing things which will break version 2 compatibility. (Heard it before ... Perl 5 to Perl 6 ... a story from or for another day).

Proposed changes include:
• moving map, filter and reduce out of the built-in namespace
• add support for optional type declarations
• unify the str/unicode types
• introduce a separate mutable bytes type
• convert built-ins to returning iterators not lists where appropriate
• remove backwards-compatibility features like classic classes and division, string exceptions, and implicit relative imports

Very VERY early days yet, so "watch this space" for news