4 ms·
I would love to use 3.x but went with 2.7.x as I need Django, and cx_Oracle. Django is 2.x only, I haven't really checked cx_Oracle.
by prog 16y ago
I would love to use 3.x but went with 2.7.x as I need Django, and cx_Oracle. Django is 2.x only, I haven't really checked cx_Oracle.
- dgallagher 16y ago...which raises the question: Does anyone know when Django plans to migrate to Python 3.x? Django 2.0 perhaps, whenever that may be?
- koenigdavidmj 16y agoThey currently are compatible back to 2.4. They want to drop one Python release per Django release (1.3 will support 2.5 and up, 1.4 will support 2.6 and up). 2.6 is the cutoff when syntax will work everywhere.
- deleted 16y ago[deleted]
- dlib 16y agoHow are they dealing with Google AppEngine's support for 2.5 when Django reaches 1.4? Or is AppEngine also expected to upgrade to 2.6 (or higher) anytime soon?
- koenigdavidmj 16y agoThey still maintain the old versions too. Last security update featured new point releases of 1.1, 1.2, and 1.3 beta. So you can just use the old version until Google get their act together.
- varikin 16y agoTechnically, Django doesn't run on GAE. All the options to get it running on GAE involve quite a bit of hacking of Django. So there really isn't any support to maintain.
- ubernostrum 16y agoNot quite. 1.3 won't be dropping support for Python 2.4, because we can't quite do that yet.
- ubernostrum 16y agoDoes anyone know when Django plans to migrate to Python 3.x? I do.
- ubernostrum 16y ago(what, people don't like a joke? I happen to know the rough timeline; when it becomes a specific timeline sometime in the very near future -- probably around the time we release 1.3 -- y'all will know about it too)
- kingkilr 16y agocx_Oracle is py3k compatible. I'm really confident we'll have Django running on py3k by the end of the summer, hopefully I'll have something exciting to announce about this coming up, but if not I'll just dedicate my summer to it.