the Gravity of Python 2

[Martijn Faassen]

Hey,

I'm pointing out possible improvements that Python 2.8 could offer that 
would help incremental porting efforts of applications. I'm pointing 
about that helping application developers move forward incrementally may 
be a worthwhile consideration. Like, there's money there.

You can point out that 2.6 and 2.7 were already such releases, and I 
will then point out that many people *have* upgraded their applications 
to these releases. Is there now going to be a giant leap forward to 
Python 3 by these projects, or is the jump still too far? Opinions differ.

On 01/08/2014 02:01 PM, Steven D'Aprano wrote:
> Adding 2.8 doesn't help. It just gives people another excuse to delay
> migrating. Then, in another two or three years, they'll demand 2.9, and put
> it off again. Then they'll insist that 15 years wasn't long enough to
> migrate their code, and demand 2.10.

I can play this kind of rhetorical game too, including demands and such 
fun. Who is demanding who does what?

It's not really a surprise that people expect there to be a compatible 
release of a programming language. We'll have to see whether the demand 
for it is strong enough to tear out community apart, or whether all will 
be right in the end.

> What's not fine though is people holding the rest of us back with their
> negativity and FUD that Python 3 is a mistake.

That's not what I believe I've been doing. Though if people do this, is 
the Python community really so fragile it can't deal with a little bit 
of pushback?

What's not fine is that people who think all is well tell the people who 
disagree to shut up. Maybe we should introduce the concept of "check 
your Python 3 privilege".

Regards,

Martijn