Re:Django 1.5 release candidate available
by zalew on Friday January 04, 2013 @02:27PM
(#5009280)
if by full you mean the whole codebase in python 3 without python 2.7 support, I guess no sooner than around 1.7 considering the deprecation scheme. currently all core code has to support both https://groups.google.com/forum/#!searchin/django-developers...
[ Parent
| on HN ]
Re:Django 1.5 release candidate available
by jacobian on Friday January 04, 2013 @03:20PM
(#5009629)
It'll likely be a bit longer than that. See my response elsewhere in this thread (https://news.ycombinator.com/item?id=5009625).
I've just read your posts here, tx for the explanation. maybe you could attach some details about it here https://docs.djangoproject.com/en/dev/internals/deprecation/?
Re:Django 1.5 release candidate available
by anderspetersson on Friday January 04, 2013 @02:53PM
(#5009447)
I would be very surprised if they deprecate python 2.7 in Django 1.7. More likely to happend when django hit 2.0. It's going to take a while until all the packages you might need for a project supports py3k.
yeah, maybe. 1.4 set minimum 2.5, 1.5 set 2.6, 1.6 will (probably) be 2.7 only. 1.7 could either stick with 2.7 and 2.0 be a py3 milestone, or it could drop 2.x and provide a py3-only codebase for developing 2.0. gotta check all the talks and announcements, I don't remember if it was decided yet.
>until all the packages you might need for a project supports py3k
I don't see it as a problem. most of them don't support py3 because django was py2.x. there is still at least a year or year and half to 1.7, it's a lot of time.