Python 2.7.7 aka the Duke Nukem Forever edition!
Gotta say I'm shocked the HN crowd downvoted this.
Extend Python 2.7 life till 2020
151–160 of 286 posts
Re: Extend Python 2.7 life till 2020
#152Earlier quoted context omitted.
IMHO there are great py3 alternatives for all of those. Which won't help you when porting, but it won't stop new applications from starting in py3 and will move the process further.
Alternatives don't help when some other project depend on a package that is not fully ported. And this is a problem. It is still a bit harder to quickly build something using Python 3.x. Check trending Python repos for this month: * portia doesn't work in 3.x because of scrapy, twisted and scrapely; * psdash - developers don't care; * jasper-client - developers don't care; * ansible - Paramico was not ported when dev…
* psdash developers don't care ? then why is this: https://github.com/Jahaja/psdash/commit/f05c8e0a1011603d5ef4...
* Twisted is getting ported. Scrapy too, according to the FAQ.
* Beets ? http://beets.radbox.org/blog/py3k.html
* PyJVM ? Who cares ?
My point being, the whole community is moving forward.
Re: Extend Python 2.7 life till 2020
#153Since there still won't be a Python 2.8, I read this as the mainstream Python not evolving one bit for the next 6 years. For me, this would be grounds for moving to a different language.
Python 3, say?
Yeah, I don't understand the argument some people have, that Python 3 is bad because it's slightly different from Python 2 and a small amount of their code won't work, so that's why they're switching to a programming language where everything is different from Python 2 and none of their code will work.
Re: Extend Python 2.7 life till 2020
#154Earlier quoted context omitted.
> I have no use of python 3 You admit you haven't done any research, so you clearly don't have any basis for making that statement.
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.
I'll let you in on a secret: Python 3 is Python, just with a couple of improvements. Painting it as an entirely new language like Perl or Scala reminds me of people I used to support who thought their entire computer was different if I gave them a monitor with a different-colored rim. You're making a mountain out of a molehill.
Re: Extend Python 2.7 life till 2020
#155Earlier quoted context omitted.
In case the grandparent doesn't realize, 2.x has a print statement not function.
Actually it's a procedure because it has a side-effect.
In python, they are called "functions" whether or not they have side effects. (And, actually, in most programming languages I've seen that have different constructs called "function" and "procedure", the difference is that functions have a return value and procedures don't -- usually, both can have side effects.)
Re: Extend Python 2.7 life till 2020
#156There are a lot of comments here from people who aren't on the python-dev list and don't really understand what this diff actually means. The core developers are not required to maintain 2.7 post-2015, and most of them won't be involved in it. That part hasn't changed. What is happening is that Red Hat is preparing to cut a RHEL 7 release, which AFAIK depending on how much you pay them they support for 13 years. So t…
There's a parallel in the Python world too: when Django 0.95 made a ton of backwards-incompatible changes, there were a lot of existing installs that simply couldn't make the jump quickly. So bugfix-only support continued, as a community project (I should know, since I helped with it), for quite some time past the official EOL.
Re: Extend Python 2.7 life till 2020
#157Earlier quoted context omitted.
IMHO there are great py3 alternatives for all of those. Which won't help you when porting, but it won't stop new applications from starting in py3 and will move the process further.
Alternatives don't help when some other project depend on a package that is not fully ported. And this is a problem. It is still a bit harder to quickly build something using Python 3.x. Check trending Python repos for this month: * portia doesn't work in 3.x because of scrapy, twisted and scrapely; * psdash - developers don't care; * jasper-client - developers don't care; * ansible - Paramico was not ported when dev…
The reason is probably because most people are still more confident writing in Python 2 and many users are using Python 2. Though many of the simple programs really don't require advance features which are only available in python 3. In other words, many of the new projects can be Python 2 and 3 compatible without effort.
Re: Extend Python 2.7 life till 2020
#158There are a lot of comments here from people who aren't on the python-dev list and don't really understand what this diff actually means. The core developers are not required to maintain 2.7 post-2015, and most of them won't be involved in it. That part hasn't changed. What is happening is that Red Hat is preparing to cut a RHEL 7 release, which AFAIK depending on how much you pay them they support for 13 years. So t…
It would be a massive strategic mistake to reject 2.x maintenance releases, or any kind of releases, on python.org as soon as 2015.
Re: Extend Python 2.7 life till 2020
#159Anyone know if RHEL 7 will ship with Python 3 in the base, even if not default? That could go a long way to boosting Python 3 adoption. I know it's in SCL, but that lacks convenience for a lot of users.
Probably. Fedora has had python3 and the related libs available as packages for years.
I am not surprised... Fedora always have the new shiny stuff. You almost never need to use "PPA" to get the latest from Fedora release to release.
Re: Extend Python 2.7 life till 2020
#160Earlier 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 ...
Well, if you were and are staying on Python 2.7, you are committing to anywhere from 6 (if you start now) to 10 (if you started day of 2.7.0 release) years of a frozen, non-evolving language. No new features, no improvements, nothing -- just the same language, for a decade.
If you can live with that, then by all means stick to 2.7 until your Red Hat support contract expires. If not, consider switching to 3.x.