Earlier quoted context omitted.
On the other hand, if you are comfortable with Python 2, it will do the job, and you know it will be supported for a foreseeable future, why bother learning Python 3? I assume there is a good answer for switching to Python 3, but I honestly don't know (haven't bothered to do any research though). Harshly put: I care about getting my python script working as soon as possible and for a foreseeable future - I couldn't c…
" why bother learning Python 3?" Unicode And of course, you'll move from a platform that's shutting down to one that's evolving Really, it's worth it.
Extend Python 2.7 life till 2020
141–150 of 286 posts
Re: Extend Python 2.7 life till 2020
#142This seems weird to me. Won't this cause a fork in Python at some point, where the 2.7 developers continue on 2.8 or rename it entirely, and another fork continues on what is now Python 3?
Python 2.7 hasn't has any improvements since python 3 began, and it won't. All this announcment means is that Python 2.7 will continue to get security/support for another 5 years.
Re: Extend Python 2.7 life till 2020
#143Earlier quoted context omitted.
Nor have I done research on Perl, Scala, etc. Your missing my point. I am successfully getting my things done in Python 2. I do not have any use for Python 3, Perl, Scala, or any other language. I might have in the future, and hey, some language might be better suited to solve the problem - but as long as it's not drastically better the sensible tradeoff is to stick with Python 2.
That philosophy sounds like one that will cause you to wake up one day and realize your skill set is massively out if date. Python 3, scala, and pearl all give you new ways of solving a problem. You're missing out on a lot of super cool stuff by not exploring! Outside of maybe library support, I see no reason to not to at least check out python 3.
>I rarely write anything high language besides small scripts. Python 2 does the job. If I ever were to need
>functionality of another language, great, it's fun to learn something new. Our time is limited and we must
>prioritize. Sadly we cannot invest time to learn everything (well I guess it's possible, but I rather be
>awesome in four languages than mediocre in twenty).
Re: Extend Python 2.7 life till 2020
#144Re: Extend Python 2.7 life till 2020
#145Earlier quoted context omitted.
" why bother learning Python 3?" Unicode And of course, you'll move from a platform that's shutting down to one that's evolving Really, it's worth it.
It's hardly shutting down if the support will last another 6 years ...
Potentially no new libraries (for new things and/or API connections)
Not sure how long new versions of existing libraries will keep 2.7 support.
Re: Extend Python 2.7 life till 2020
#146This seems weird to me. Won't this cause a fork in Python at some point, where the 2.7 developers continue on 2.8 or rename it entirely, and another fork continues on what is now Python 3?
Re: Extend Python 2.7 life till 2020
#147Earlier quoted context omitted.
> I for one like the 2.x style print function. 2.x didn't have a print function, unless you mean the one from 3 available with a from __future__ import.
In case the grandparent doesn't realize, 2.x has a print statement not function.
Re: Extend Python 2.7 life till 2020
#148This is really disappointing to see - I fear that it will slow adoption of Python 3 even further, when it was just reaching a tipping point[0]. When I first learned Python, I learned Python 3 first because it was newer, and I figured everyone would be using it soon enough. Little did I know that Python 2 would continue to be supported for over ten years after that! Some people make a big deal about figuring out "whic…
On the other hand, if you are comfortable with Python 2, it will do the job, and you know it will be supported for a foreseeable future, why bother learning Python 3? I assume there is a good answer for switching to Python 3, but I honestly don't know (haven't bothered to do any research though). Harshly put: I care about getting my python script working as soon as possible and for a foreseeable future - I couldn't c…
This bothers/worries me, because I don't understand where this notion that "learning Python 3" requires significant effort or commitment comes from. Python 3 isn't massively different from Python 2. I learn more "new stuff" (APIs I've never used before, implementation details of systems I work on/with, etc.) basically every month than that difference.
Python 2 -> 3 can be a big step because of dependencies. The difference between the languages themselves is negligible (and yet, IMHO for the better). You don't need to learn any new ways of thinking here.
If you're comfortable with Python 2, you're comfortable with Python 3 as well. If your dep ducks are in a row and you're writing new code, it's an obvious choice.
Re: Extend Python 2.7 life till 2020
#149Earlier quoted context omitted.
In case the grandparent doesn't realize, 2.x has a print statement not function.
I meant function as in functionality. This is really pointless nitpicking.
Re: Extend Python 2.7 life till 2020
#150This is really disappointing to see - I fear that it will slow adoption of Python 3 even further, when it was just reaching a tipping point[0]. When I first learned Python, I learned Python 3 first because it was newer, and I figured everyone would be using it soon enough. Little did I know that Python 2 would continue to be supported for over ten years after that! Some people make a big deal about figuring out "whic…