LWN: Comments on "Python Python Python (aka Python 3) (Linux Journal)"

Python Python Python (aka Python 3) (Linux Journal)

pboddie — Tue, 11 Aug 2009 10:35:53 +0000

And I would claim that Python doesn't need Python 3 to be a success like Perl needs Perl 6 to be a success. Moreover, a lot of the activity around improving Python performance has been happening on Python 2 variants - it's not like everyone has to bet on Python 3 becoming dominant in order to enjoy the benefits of such efforts.

Python Python Python (aka Python 3) (Linux Journal)

malefic — Tue, 11 Aug 2009 03:32:14 +0000

In order to boost adoption, Python 3 has to provide some strong incentive. One such thing might be merging Unladen Swallow into the py3 branch (only). That seems too artificial, though. I, personally, base all my new projects on Python 3 and don't look back. Certainly, it takes some effort to port the required subset of third-party code, but the benefits of Python 3 cleanups outweigh the burden.

Python Python Python (aka Python 3) (Linux Journal)

b7j0c — Mon, 10 Aug 2009 22:53:16 +0000

jump to v3? some key libs like mysql bindings haven't even jumped to 2.6.

because python3 isn't radically different or even obviously different to most coders, my guess is very few will feel a fire burning underneath them to jump on the v3 bandwagon. the universe will be in a state of abject contradiction if perl6 ends up taking off faster than python3...lets see where things stand next summer

Python Python Python (aka Python 3) (Linux Journal)

djc — Mon, 10 Aug 2009 20:35:37 +0000

FWIW, Mercurial has GSoC project this summer which is also looking at putting py3 support in the same code base.

Python Python Python (aka Python 3) (Linux Journal)

jordanb — Mon, 10 Aug 2009 16:37:55 +0000

A big problem is that a lot of utilities people depend on don't work with it. A big thorn in my side is virtualenv. Worse, there's not been a squeak out of Ian on the subject even though there's an open bug since last December.

I guess at some point someone outside the project is going to have to wade into it and figure out how it all plugs into Python 2.0, if Ian has lost interest. :<

[0] https://bugs.launchpad.net/virtualenv/+bug/307026