3 ms·

Very much looking forward to using 1.7! Question for all: Would now be a good time to move to Python 3.x? Our current Django installations are all running 2.7,

by shijie 12y ago

Very much looking forward to using 1.7! Question for all: Would now be a good time to move to Python 3.x? Our current Django installations are all running 2.7, and we are thinking about switching just for better unicode support alone. I'd love to hear some of your thoughts on this.

Walkman 12y ago
If your database backend is not MySQL, then I would say yes. For MySQL you need to think about which database adapter you choose. You can search for earlier topics in HN about the topic, but the state of Python 3 is not bad at all!
mstrcnvs 12y ago
Django fully supports Python 3 from version 1.5. If you can use it or not depends more on the other packages you might have installed like DB adapters, image processing, etc. https://caniusepython3.com https://caniusepython3.com is a good way to know, you just need to drop your requirements.txt and it will tell you!
- jsmeaton 12y ago
  Further, if you find a dependency that isn't supported, you should check the projects site to see if support is on the road map. You could also try contributing the python 3 upgrade to that package. I recently began a new site based on django 1.7 (RC) and python 3.3, and only a single package I needed wasn't available. Someone had already opened a PR for py3 support though, so some gentle prodding got it merged within a week.
techdragon 12y ago
As others are mentioning, there are places you can check general python3 support. But more specifically, if you want to check your django python3 support, you should have a good browse around http://www.djangopackages.com http://www.djangopackages.com
yuvadam 12y ago
I recently started a new Django 1.7 (beta/RC until now) + Py3 project, and it's going great. All the major dependencies work flawlessly on Py3. I did have some problems with some minor API wrapper libraries, but those can easily be patched or other written to support the needed functionality. Regarding a full-on migration, I haven't done that yet on any of my larger existing projects. As with any migration I'd be careful to weigh the cost/benefit of such a move. But, at least from my experience in this field, Py3 is definitely ready for prime time. Use it!

by shijie 12y ago

Walkman 12y ago

If your database backend is not MySQL, then I would say yes. For MySQL you need to think about which database adapter you choose. You can search for earlier topics in HN about the topic, but the state of Python 3 is not bad at all!

mstrcnvs 12y ago

Django fully supports Python 3 from version 1.5. If you can use it or not depends more on the other packages you might have installed like DB adapters, image processing, etc. https://caniusepython3.com https://caniusepython3.com is a good way to know, you just need to drop your requirements.txt and it will tell you!

jsmeaton 12y ago
Further, if you find a dependency that isn't supported, you should check the projects site to see if support is on the road map. You could also try contributing the python 3 upgrade to that package. I recently began a new site based on django 1.7 (RC) and python 3.3, and only a single package I needed wasn't available. Someone had already opened a PR for py3 support though, so some gentle prodding got it merged within a week.

techdragon 12y ago

As others are mentioning, there are places you can check general python3 support. But more specifically, if you want to check your django python3 support, you should have a good browse around http://www.djangopackages.com http://www.djangopackages.com

yuvadam 12y ago

I recently started a new Django 1.7 (beta/RC until now) + Py3 project, and it's going great. All the major dependencies work flawlessly on Py3. I did have some problems with some minor API wrapper libraries, but those can easily be patched or other written to support the needed functionality. Regarding a full-on migration, I haven't done that yet on any of my larger existing projects. As with any migration I'd be careful to weigh the cost/benefit of such a move. But, at least from my experience in this field, Py3 is definitely ready for prime time. Use it!