previous releases were incompatibilie with earlier ones unintentinally.

Where's the mac version..?

But I just came in here for an argument!

So what are you going to do, take all your existing Python applications and rewrite them in a different language, in order to avoid the "significant amount of work to maintain existing functionality with new language version"?

Nope. Python 3.11 for Workgroups.

As someone mentioned above, try

from __future__ import braces

and see what happens. ;)

As for Ruby, I don't really follow its development or use it, but I was reading just the other day that they're really focused on finishing 1.9, which does byte-compiling and some optimization. The current version (like JS before spidermonkey, V8, and squirrelfish) walks and executes the AST (as I understand it), which is slooow.

That'll be when Perl 6.0 ships.

I heard they're going to use Python 3.0 for the impending from-scratch rewrite of DNF.

No you didn't.

Thus the phrases "The looooooooooong tail" and "You're ALL tail, baby".

Are you typing while drunk?

You seem to want Perl. You can find it at http://www.perl.org/ [perl.org]

Interestingly, it IS backwards compatible in areas that you wouldn't think it should be. For instance, the following program takes the version number, adds one to it, and divides by two. You'd think it'd give a different answer between version 3 and version 2. Glad they kept this program working for me, as it's the secret production code that runs my multi-million dollar business.

import sys
version=int(sys.version[0])
print (version+1)/2

Prints 1 in either version. (on the bright side, 1/2 is now 0.5!)

Signs of the apocalypse:

* A black man was elected President of the US - November 4, 2008
* Chinese Democracy was released - November 23, 2008
* Python 3000 is released - December 4, 2008
* ?
* ?
* Large Hadron Collider starts operations - ?
* Duke Nukem Forever is released - ?

No, he generated that comment with Python 2.6 code but ran it with the new release.

An argument isn't just contradiction!

Yes it is.

True Part:
In Python version 2, 1/2 = 1 (integer math)
In Python version 3, 1/2 =0.5 (floating point math)

Funny part:
You can do some math on the version number and it comes out the same, even though the version number has changed. Because the divide operation changed too.

wait, it's not so funny after all. What was I smoking?

>You download the .tart.gz or .tar.bz2 source packages and build it. \

At last, what the world has been waiting for: a language for bimbos and airheads! :)

hawk

WTF are you talking about? Visual Basic has been around since 1991!

I think you got that wrong. A hammer usually isn't considered very subtle.

Out of interest, why did they decide to calculate 1/2 as float in Python 3?

We got sick of explaining integer math to newbies on the python list each and every single day. So it was decided that if we used '//' for integer division and let '/' do what newbs expect we'd be saving ourselves muchos keystrokes in the long run.

I'm glad you brought that up, I can't believe that there is not a single other post or discussion thread here regarding whitespace in Python. I've always wondered why, whenever there's a story about Python on Slashdot or Ars or wherever, there's never, ever, ever even one single comment about how Python deals with whitespace. But you, sir, have broken the seal! Bravo.

It's scary to code something while drunk then come back the next day and think "god, whoever wrote this is clever".

I don't even need to be drunk! That happens to me regularly ... ah the ageing process.