> Does this mean that Django is ready to use with Python 3? Not yet!
Yes, there are devs/companies embracing python 3, but not enough :( . As I said in my article a few people think it would be better to throw python 3 away. I don't understand why.
Most developers I know are upset about the amount of unnecessary work that porting their code to Python 3 causes, and vent that justified frustration (or just don't port). A few are upset over the direction Python seems to be going in.
I don't know very many who would classify their opinion objectively as "we think it would be better to throw Python 3 away".
Comments
From : https://www.djangoproject.com/weblog/2012/aug/19/experimenta...
> Does this mean that Django is ready to use with Python 3? Not yet!
Yes, there are devs/companies embracing python 3, but not enough :( . As I said in my article a few people think it would be better to throw python 3 away. I don't understand why.
Most developers I know are upset about the amount of unnecessary work that porting their code to Python 3 causes, and vent that justified frustration (or just don't port). A few are upset over the direction Python seems to be going in.
I don't know very many who would classify their opinion objectively as "we think it would be better to throw Python 3 away".