11–20 of 59 posts
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 [2]: https://www.djangoproject.com/weblog/2012/mar/13/py3k/
I can never be surprised enough how people are excited about django features that others take for granted.
Best thing I've seen all day. (Go ahead and downvote me, this comment has absolutely value, yet despite knowing that I'm so happy I still feel compelled to post it. :)
- the porting strategy is explained here: https://docs.djangoproject.com/en/dev/topics/python3/
- the porting work happens in the master branch; commits related to the Python 3 port are usually prefixed by [py3]: https://github.com/django/django/commits/master
- the test suite doesn't pass yet, but the hardest part is done: http://ci.djangoproject.com/job/Django%20Python3/
- most of the work happened over the last three weeks, and 5 or 6 core developers are contributing significantly
Best thing I've seen all day. (Go ahead and downvote me, this comment has absolutely value, yet despite knowing that I'm so happy I still feel compelled to post it. :)
I'm apathetic, but please let's not start the trend of self-aware "downvote me" or "why the downvotes?" comments on this website. I'm of the opinion that it's needless, manipulative clutter.
As long as there aren't a bunch of "me too" comments, of course.
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 [2]: https://www.djangoproject.com/weblog/2012/mar/13/py3k/
yeah 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.
Well, the authors of frameworks and libraries still on Python 2 and without having concrete upgrade plans will have to either do something soon or others will take their space. Python 3 is here, now.
Do you know of anything new on PIL (http://www.pythonware.com/products/pil/) ? Or any similar library that might replace it for Python 3?
Well, the authors of frameworks and libraries still on Python 2 and without having concrete upgrade plans will have to either do something soon or others will take their space. Python 3 is here, now.
> the authors of frameworks and libraries still on Python 2 and without having concrete upgrade plans will have to either do something soon or others will take their space. Do you know of anything new on PIL ( http://www.pythonware.com/products/pil/ ) ? Or any similar library that might replace it for Python 3?