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

Question

I ask this for deployable reasons. As in, if I write a solution in python, I feel bound to write to 2.x due to the lack of adoption of python 3. This is a major daily concern of mine, and I want to figure out what's going on.

For many of the python-based questions here, people are giving solutions that simply do not work in python 3.x.

So, I ask the question: What has prevented you from switching to python 3.x in your personal or work environment? The conversion script exists, and yet programmers (who are usually the earliest adopters of everything) seem to refuse to upgrade.

Why?

Answer 1

[Edit 03/10/2014: This answer is now out-of-date. Django has supported Python 3 for some time.]

[However, it must also be noted that the django third-party packages and extensions used in many Django projects are in various stages of Python 3 compatibility implementation. More details can be found in Django packages website which tracks the statuses of various projects.]

Django has not moved over to 3.0. That is all I need to know.

Related Questions

• Will Python 3.0’s backwards-incompatibility affect adoption?
• Is Python 3 a good starting point when you want to learn Python?
• If I’m going to learn Python, should I learn 2.x or just jump into 3.0?
• Who’s Using Python 3.0?
• Python Version for a Newbie
• Is it worth learning Python 2.6 with 3.0 coming?

Most of the answers in these questions echo the same sentiments. Aside from Django, too many frameworks/libraries - WxPython, PyGame, Django, etc - have still not adopted it. I'm sure as hell not making the move until they do.

Answer 2

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.