Re:Writing Python 2.x forward compatible to Python 3 code
by koenigdavidmj on Saturday January 22, 2011 @01:38PM
(#2130772)
They 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.
[ Parent
| on HN ]
Re:Writing Python 2.x forward compatible to Python 3 code
by dlib on Saturday January 22, 2011 @02:49PM
(#2130907)
How 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?
Re:Writing Python 2.x forward compatible to Python 3 code
by koenigdavidmj on Saturday January 22, 2011 @02:53PM
(#2130921)
They 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.
Re:Writing Python 2.x forward compatible to Python 3 code
by varikin on Sunday January 23, 2011 @10:13AM
(#2132493)
Technically, 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.
Re:Writing Python 2.x forward compatible to Python 3 code
by ubernostrum on Sunday January 23, 2011 @06:02AM
(#2132226)
Not quite. 1.3 won't be dropping support for Python 2.4, because we can't quite do that yet.