[grokaholic]

Django's lack of Python 3 support is big reason Python 3 adoption is slow, at least in the web dev faction of Python's community.

Why get comfy with Python 3 when you must remain attuned to the conventions and quirks of 2.x in order to use Python's most popular web framework? Folks keep talking about Python 3 because they really want to use it, but have reservations about adopting 3 when 3 isn't supported by useful frameworks.

Once Django supports Python 3, that reservation vanishes. Python 3 will be adopted by more people and get support from more frameworks.

tl:dr; Django's popularity holds dev community captive to Python 2.x, slows adoption of Python 3. Django team announces Python 3 support not in distant future but near future. Folks get excited. "About damn time."

[rlander]

Python != Web frameworks

You're severely underestimating the impact that the scientific computing community has over Python 3's slow adoption.

[cdavid]

I don't understand your statement. Numpy has been ported on python 3 more than 18 months ago, and scipy followed quickly afterwards. Our download stats show rather little interest for python 3, BTW.

[dagw]

The numpy and scipy core may have been ported, but many of the Scikits (add on libraries to scipy), third party libraries and surrounding tools haven't. So most people will still go with python2 just in case they might need to use one of those tools or libraries later down the road.

[timc3]

Personally the only reason that I am not using Python 3 right now is that Django doesn't support it, as that is the main library that I am supporting and using everyday.

Other libraries I use are smaller, can be replaced, or I could rewrite them.

I am quite sure that I am not in a minority.

[superxor]

+1 I had started learning Python 3. But my job now is on Django, so I am forced to use Python 2. I know a good number of people who had the same problem.