Why won't you switch to Python 3.x? [closed]

Answer 1

Python 3+ does not support numpy. Correction: it now does. As it now supports mathplotlib.

Answer 2

1. Compiled 3rd party modules haven't updated.
2. Different syntax
3. Slower integers.
4. The #python IRC channel on freenode has in its title that its too early to switch.

Answer 3

Because of the lack of backward compatibility, switching is hard, especially if there is C code involved. And although I understand the unicode/string thing may be very useful to some people, I certainly don't care about it myself.

Basically, Py3k did not solve many problem that I care about (distribution issues, versioning of modules, simplified import model).

Answer 4

Because the default installation of 2.5 on Mac OSX Leopard works just fine. I have no need to upgrade and I see no advantage to upgrading except an end to the woes of unicode.

Answer 5

The main reason I am not switching is that so many books and coding challenge websites are still 2.x. I installed 3.x and realized very quickly that I had to uninstall and go to 2.x.

Answer 6

Because major libraries that my codebase depends upon have not released a 3.x version. (wxPython, matplotlib, numpy, etc.)

So the responsibility goes upstream from my point of view.

If all my dependencies were 3.x compatible, I'd probably have switched by now.