On: Python 3 can revive Python

[e12e]

> No matter how fast the OS can spin up another process, you still have to contend with the overhead of Python initialization itself.

Good point... but isn't part of that possible to reduce a little when python itself forks? I've not looked at the code, that might very well not be what happens when you use the multiprocess-module?

> And I don't quite understand what you mean by the "full number tower".

I was thinking of: http://legacy.python.org/dev/peps/pep-3141/

but apparently confused as to what had changed in python3 (mostly the change to division/true division -- which I still think is more pythonic, but less of a change than I thought).

So eg:

    $ python2 -c "print(1/2)"
    0
    $ python3 -c "print(1/2)"
    0.5

But I also thought there might be some differences wrt doing stuff like:

     $ python -c "print(2**10000)"
     19950(...)9376

But there isn't :-)

[maxerickson → e12e]

In 2.x, ints and longs are separate types. It's largely transparent though.