4 ms·
Not only a major boost for Python 3 adoption but also a reference for how Unicode handling [1] can be successfully ported from Python 2.x libraries. They seem
by arocks 14y ago
Not only a major boost for Python 3 adoption but also a reference for how Unicode handling [1] can be successfully ported from Python 2.x libraries.
They seem to be on schedule as well, which is brilliant [2].
[1]: http://wiki.python.org/moin/PortingDjangoTo3k http://wiki.python.org/moin/PortingDjangoTo3k
[2]: https://www.djangoproject.com/weblog/2012/mar/13/py3k/ https://www.djangoproject.com/weblog/2012/mar/13/py3k/
- ergo14 14y agoyeah we already had in Pyramid 1.3 for ages ;-) I can never be surprised enough how people are excited about django features that others take for granted.
- hcarvalhoalves 14y agoMaybe because they care about Django, not Pyramid?
- deleted 14y ago[deleted]
- aptwebapps 14y agoDo you think they are excited because they are amazed a framework could do such things or maybe because they are happy that the framework they use can now do such things? Does anyone get excited at the mere thought that some framework, somewhere has a particular feature? If you aren't using Pyramid then what good does it do you?
- SiVal 14y agoHow well does Pyramid work with Python 3 (production ready)? And what are the pros and cons of Pyramid vs. Flask or some other lighter weight way to build web apps with Python 3?
- ergo14 14y agoAs far as I can tell, many people use it in production just fine. As for Pyramid vs. Flask, well pyramid gives you more, but you can use it flask-like if you want.