News for hackers. Stuff that matters.
Re:Django 1.5 release candidate available by rednukleus on Friday January 04, 2013 @02:21PM (#5009241)
Great! Does anyone have an estimate of when full Python 3 support is expected?
Re:Django 1.5 release candidate available by jacobian on Friday January 04, 2013 @02:58PM (#5009484)
So here's the deal:

Django 1.5 has "full" Python 3 support, at least from a technical level. It's done, works, is well-tested. I'm planning on putting a Django 1.5 / Python 3.3 site into production later this year. So in that sense it's "done" now.

However, we sorta have to hedge our bets in terms of what we recommend others do.

We have a pretty serious backwards-compatibility promise, and we're not 100% certainly we've nailed down all the Python 3 APIs perfectly. There's a small (but non-zero) chance something might need to change between 1.5 and 1.6; we want the ability to make that change backwards-incompatible (for Python 3 users) if possible.

Similarly, there's a small (but again non-zero) chance that there's a serious bug or three in the Python 3 support. We don't want people getting bitten.

Finally, much of the "good stuff" in Django-land is actually in third-party apps, many of which don't yet support Python 3. This puts a pretty big obstacle in the way of a Django/Py3 site -- most real-world sites use a ton of third-party stuff. So to use Django on Py3 right now you'll need to make a bunch of "should I DIY this component or port it to py3 and submit a patch?" decisions.

In the case of the site I mentioned up top these are tradeoffs I'm willing to make. I know Django well enough to not be worried about potential bugs or backwards-incompatibilities, and I have the luxury on this project of getting to work on py3 patches as part of the deal.

Most people won't be so lucky, though, so we expect the majority of Django users to wait until 1.6 to start seriously using Py3.

We don't have a firm timeline yet. I'm guessing something like 6-9 months for 1.6, but that depends on a lot of different things. It could be longer, as much as a year, or possibly even as short as 3-4 months. We'll see :)

Re:Django 1.5 release candidate available by mahmoudimus on Friday January 04, 2013 @03:05PM (#5009533)
This is such a great answer. Definitely understand the reasoning here -- part of Django's strength is its ecosystem and its available third-party apps. Taking that away would certainly hinder adoption/productivity.

At the same time, it's important to realize that there will probably need to be some point in the future where Django has to take a stand and firmly put down a timeline on when apps need to be migrated to stay "relevant."

Maybe something like Python's Wall of Superpowers / Shame (http://python3wos.appspot.com/) though I know Jesse Noller has had some pushback on this website.

Re:Django 1.5 release candidate available by jnoller on Friday January 04, 2013 @03:36PM (#5009719)
I didn't have pushback. I didn't like the "Wall of Shame" name.
Re:Django 1.5 release candidate available by mahmoudimus on Friday January 04, 2013 @03:39PM (#5009731)
Ah fair enough!
Re:Django 1.5 release candidate available by ambiate on Friday January 04, 2013 @03:09PM (#5009556)
Is there a non-zero chance that all Python 2.* support will be removed in the future (2-3 years)? I'm with a company that's currently toying with the idea of using Django in our production environment. Py3 is a no-show in our plan or goals.
Re:Django 1.5 release candidate available by jacobian on Friday January 04, 2013 @03:20PM (#5009625)
At some point, yes, we'll drop Python 2 support. When really depends on how rapidly we see adoption (from users and re-distributors of Django) and how heavy the dual-version support burden turns out to be. My guess is what we're looking at a longer support window than the 2-3 years you posit, but that's really just a half-assed guess. Anything between "next year" and "never" would be a reasonable guess too...

... and y'know, Python 3 should be on your radar, if not necessarily what you use right now. It's better than Python 2 in every way (except for adoption, and that's changing). 3.3 in particular has a ton of really great new stuff (futures! working namespace packages! yield from!) that you'll wonder how you lived without.

Re:Django 1.5 release candidate available by gtaylor on Friday January 04, 2013 @03:31PM (#5009699)
This! I'm so glad to hear this straight from one of the maintainers. Python 3.3 is the first version of Python 3 that has made me stop and say, "Wow, this really makes my life easier/better". The sooner we as an ecosystem get moving on, the better.
Re:Django 1.5 release candidate available by kenneth_reitz on Friday January 04, 2013 @10:36PM (#5011432)
It's going to get worse before it gets better.

But, it'll be worth it.

Re:Django 1.5 release candidate available by SiVal on Saturday January 05, 2013 @07:22AM (#5012423)
I'm glad to hear it. Just as additional feedback: Python 2 is a "no show" in our future plans. We got over the upgrade hurdle years ago and have no intention of walking back into it. Anything stuck in Python legacy-land may as well be COBOL as far as we're concerned. We prefer Python 3 when it's available, but we use languages other than Python when there is no Python 3 solution.
Re:Django 1.5 release candidate available by ambiate on Friday January 04, 2013 @04:10PM (#5009923)
Thanks, I appreciate your time.
Re:Django 1.5 release candidate available by gtaylor on Friday January 04, 2013 @03:13PM (#5009576)
They've been gradually removing support for older Python 2.x with each release, so it's likely the same will happen with all of Python 2 in the coming years.

But that's probably a good thing. Python needs to keep improving, and Python 3 is just flat out a better language.

Re:Django 1.5 release candidate available by mixmastamyk on Friday January 04, 2013 @06:56PM (#5010699)
Isn't it still significantly slower? Even though it probably doesn't matter most of the time, it would helpful for all 3's items to be in the "better column."
Re:Django 1.5 release candidate available by tshepang on Saturday January 05, 2013 @06:39AM (#5012346)
The only significant slowness I've heard of was due to the I/O library, but it was only in 3.0, so has since been fixed. Or were you referring to something else?
Re:Django 1.5 release candidate available by SilasX on Friday January 04, 2013 @03:18PM (#5009616)
That care and precision, in a nutshell, is a large part of why I prefer Django to Rails so much.
Re:Django 1.5 release candidate available by rednukleus on Friday January 04, 2013 @03:24PM (#5009655)
Thanks for the detailed answer! That all makes sense, and sounds like a very sensible way for the project to progress.
Re:Django 1.5 release candidate available by eclipticplane on Friday January 04, 2013 @05:53PM (#5010483)
As an author of many Django sites and third party components/libraries -- Django was one of our major blockers to even attempt Py3 ports. Now that it's under way, we'll get started, too. The fact that Django is using a single code base (with six) is a huge bonus, so we'll be trying to do that, too.
Re:Django 1.5 release candidate available by clicks on Friday January 04, 2013 @02:27PM (#5009275)
Considering minor releases happen every 8 months or so (i.e., Django 1.6 will be released latter half of this year), I'm thinking that'll be enough time to work out the kinks for running Django on Python 3.

I do want to point out that it was only last year people used to say that Django was _the_ thing holding everyone going from Python 2 -> Python 3. And now Django has made the move, -- others (Flask, etc.) have not.

Re:Django 1.5 release candidate available by huxley on Friday January 04, 2013 @03:23PM (#5009649)
Django 1.6 wouldn't be a minor release, 1.x are major versions.

You're more likely to see an alpha release of 1.6 in 8 months, the final released versions of Django have a roughly annual release schedule:

* Django 1.4 came out March 23, 2012

* Django 1.3 came out March 23, 2011

* Django 1.2 came out May 17, 2010

* Django 1.1 came out July 29, 2009

* Django 1.0 released September 3, 2008

Update: Didn't read the part of Jacob Kaplan-Moss' response above where he says 1.6 could be coming in "6-9 months" and as in as little as 3 months. To which I'd say "Wow"

[deleted]
Re:Django 1.5 release candidate available by huxley on Friday January 04, 2013 @03:41PM (#5009748)
Well, dang, I stand corrected.

As a Django user, I've always understood Django 1.x to follow the Apple convention with OS X numbering. To the credit of the core team, every minor release has felt like a major improvement to me.

Re:Django 1.5 release candidate available by takluyver on Saturday January 05, 2013 @07:43AM (#5012460)
Many projects roughly follow 'semantic versioning'. You change the first number for a release that breaks backwards compatibility, the second number for a feature release, and the third number for a bugfix release.
Re:Django 1.5 release candidate available by jacobian on Friday January 04, 2013 @03:30PM (#5009695)
Well... 3 months is possible, but unlikely. 6-9 is more likely. 12 months is unlikely, but more likely than 3.
Re:Django 1.5 release candidate available by dtwwtd on Friday January 04, 2013 @09:00PM (#5011072)
Tornado has supported Python 3 since mid-2011.

http://www.tornadoweb.org/documentation/releases/v2.0.0.html

Re:Django 1.5 release candidate available by rednukleus on Friday January 04, 2013 @02:30PM (#5009297)
Thanks, that was the answer I was looking for.
Re:Django 1.5 release candidate available by agildehaus on Friday January 04, 2013 @02:26PM (#5009268)
"We plan to offer first-class, production-ready support for Python 3 in our next release, Django 1.6."
Re:Django 1.5 release candidate available by rednukleus on Friday January 04, 2013 @02:27PM (#5009281)
What I mean is, when is 1.6 expected to land?
Re:Django 1.5 release candidate available by agildehaus on Friday January 04, 2013 @02:29PM (#5009294)
When it's done, of course!
Re:Django 1.5 release candidate available by rednukleus on Friday January 04, 2013 @02:48PM (#5009418)
Grumble...
Re:Django 1.5 release candidate available by yareally on Friday January 04, 2013 @11:55PM (#5011662)
You didn't really expect a concrete answer, did you? You can take a guess by looking at http://news.ycombinator.com/item?id=5009649
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...
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).
Re:Django 1.5 release candidate available by zalew on Saturday January 05, 2013 @03:04AM (#5012056)
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.
Re:Django 1.5 release candidate available by zalew on Friday January 04, 2013 @03:11PM (#5009572)
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.

Re:Django 1.5 release candidate available by greghinch on Friday January 04, 2013 @02:24PM (#5009257)
Last line of the note is a link to the plan for full Python 3 support

https://www.djangoproject.com/weblog/2012/aug/19/experimenta...

Re:Django 1.5 release candidate available by rednukleus on Friday January 04, 2013 @02:27PM (#5009273)
There is no date or timeline, I was wondering if this was a "Next 6 months" thing or if it will take a lot longer.
Re:Django 1.5 release candidate available by greghinch on Friday January 04, 2013 @03:00PM (#5009502)
I think the point is they don't know yet. 1.5 is intended to get the early version in front of a wide audience, shake out the issues, and then they can make a call on timeframe.