I believe the non-backward compatibility of Python 3.0 and the monopolization of major conferences by Django (which was great 5 years ago but it loses to most of the other frameworks by now) are part of the cause.
The other cause I think the raise of multi core processors. Python does not handle them well. The only option is multi-process applications but their are not very easy to write. This is not a problem for web applications. I also think the drop to be significant although not necessarily a long term trend. Python could rebound easily by: - extending the life of 2.x with 2.8 (including as much goodies from 3.x as possible but backward compatibility) and promising LTS - merging stackles and/or gevent - including a standard request/response objects in the libraries - include the request library as replacement for urlib/urlib2 - provide a windows distribution which includes PIL/NumPi/SciPy and is not commercial - stop the Django community from monopolizing every forum (it is still losing to Rails and therefore not the future) and emphasize diversity. - stop the purists who do bash Python projects that are working and popular for not being Pythonic (whatever it means, you do not hear of Java projects not being Javonic). - go back to target schools. I was at PyCon and it is mostly a recruiting place where consultants advertise themselves and their companies. Very few talks are technical. Meanwhile many schools are moving away from Python in favor of JavaScript. This makes no sense to me but perhaps there is something that can be done. Massimo On Thursday, 29 March 2012 08:42:08 UTC-5, Ovidio Marinho wrote: > > The fall of the python's fault Django and Python 3.0? > http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html >
