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.
[ Parent
| on HN ]
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.
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.
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.
Thanks, I appreciate your time.
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."