[Python-ideas] Proposal to change Python version release cycle

M.-A. Lemburg mal at egenix.com
Sun Nov 5 08:48:39 EST 2017

On 04.11.2017 20:33, Nick Timkovich wrote:
> On Sat, Nov 4, 2017 at 10:44 AM, M.-A. Lemburg <mal at egenix.com> wrote:
>> Just to clarify: Python 2.0 was called 2.0 because the BeOpen marketing
>> department thought it was good idea, not because there were major
>> incompatible changes going into that release.
> Alternative history question: if it was just 1.6, then would Python 3000,
> probably called "Python 2000/2.x" in that world, with all the fixes have
> happened sooner because you would have "ran out" (yes, v1.10 > v1.9) of
> numbers leading up to 2?

There was a Python 1.6, but this was cut during the Python 2.0
release cycle to make CNRI happy. It included everything
the CNRI team had developed after Python 1.5.2 before
moving on to BeOpen to form the "PythonLabs":


See "Overview of Changes Since 1.6" in
for a list of changes between 1.6 and 2.0.

The Python 1.6 never went into wide distribution, so for all
practical purposes the move was from Python 1.5.2 to
Python 2.0.

More on all this is available in the "What's New in Python 2.0"


Marc-Andre Lemburg

Professional Python Services directly from the Experts (#1, Nov 05 2017)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611

More information about the Python-ideas mailing list