[Python-Dev] PEPS, version control, release intervals

[Tim Peters]

[Paul Barrett]
> ...
> I think people are moving to 2.0, but not at the rate of
> keeping-up with the current release cycle.

It varies by individual.

> By the time 2/3 of them have installed 2.0, 2.1 will be released.

No idea.  Perhaps it's 60%, perhaps 90%, perhaps 10% -- we have no way to
tell.  FWIW, we almost never see a bug report against 1.5.2 anymore, and bug
reports are about the only hard feedback we get.

> So what's the point of installing 2.0, when a few weeks later,
> you have to install 2.1?

Overlooking that you don't have to install anything, the point also varies
by individual, from new-feature envy to finally getting some 1.5.2 bug off
your back.

> The situation at our institution is a good indicator of this: 2.0
> becomes the default this week.

Despite you challenging them with "what's the point?" <wink>?  Your
organization's adoption schedule need not have anything in common with
Python's release schedule, and it sounds like your organization moves slowly
enough that you may want to skip 2.1 and wait for 2.2.  Fine by me!  Do you
see harm in that?  It's not like we're counting on upgrade fees to fund the
next round of development.