Live data from Hacker News

Most popular Python packages now support Python 3

py3readiness.org

71–80 of 166 posts

Re: Most popular Python packages now support Python 3

#71
post #40

I have extreme Python 2-vs-3 fatigue and that's only from seeing the topic on news aggregators for years on end. I can't fathom how tedious the topic must be for those actually in the Python community for the whole time.

It's not really bad anymore. I moved to 3 about two years ago now, and haven't looked back. There was a brief period of working with polyfilled six hacks, but currently the community and momentum are largely behind 3.

There was a point where there was some FUD around the migration, painting it as a sequel to PERL 6. However, the community managed to turn it around. To their credit, orchestrating large breaking changes to a popular language with a diverse set of use cases is fundamentally a very challenging task.

The main holdouts for Python 2 are large organizations which have a lot of existing/working legacy code. The majority of new Python projects seem to be using Python 3.

Now that the work is nearly done, we can all enjoy a better Python.

I very recently moved to 3.6, from 3.5. There's a saying that a luxury once sampled becomes a necessity, which sums up my opinion on the new f-string syntax.

Re: Most popular Python packages now support Python 3

#72

Yup at this point there is no reason to not use Python 3 for new projects. What I'm finding actually is that some companies that have their codebase in Python 2 have actually started migrating to Golang rather than Python 3, because of the increased performance benefits. I'm kind of sad about this, but I think that Golang will eventually replace Python as the go-to back-end server language (maybe even data processing…

> at this point there is no reason to not use Python 3 for new projects

Sure there is: Python 2 isn't going to change on me again. Python 3 might.

Re: Most popular Python packages now support Python 3

#74

Yup at this point there is no reason to not use Python 3 for new projects. What I'm finding actually is that some companies that have their codebase in Python 2 have actually started migrating to Golang rather than Python 3, because of the increased performance benefits. I'm kind of sad about this, but I think that Golang will eventually replace Python as the go-to back-end server language (maybe even data processing…

> at this point there is no reason to not use Python 3 for new projects Sure there is: Python 2 isn't going to change on me again. Python 3 might.

Why on earth do people downvote that? I want a language that isn't going to change. Every single other language community seems to understand that, but something about it pisses off Python people.

Re: Most popular Python packages now support Python 3

#75
post #40

I have extreme Python 2-vs-3 fatigue and that's only from seeing the topic on news aggregators for years on end. I can't fathom how tedious the topic must be for those actually in the Python community for the whole time.

Rather heavy Python user here, though a little bit less over the last year: I think the whole thing is largely overblown. I've fully migrated to Python3 three years ago, was expecting horror given all the articles and 2vs3 drama, yet it was done very quickly and painlessly.

I've gone through migrations that were much more tedious and painful. Not so much with languages but with dependencies/frameworks: the like of Django, Django-rest-framework, Unity 3D, and pretty much anything javascript (apart from javascript itself).

Re: Most popular Python packages now support Python 3

#76

Earlier quoted context omitted.

Yup. And the developers learned their lesson and aren't going to do it again. https://www.curiousefficiency.org/posts/2014/08/python-4000....

Given the Python versioning effective convention, it would be strange for the developers to go from 3.9 -> 4.0 because they've run out of digits. Probably better to go to 3.10 to avoid confusion and stay on 3.X while there's no backwards-compatible breaks.

Yup. They eventually decided they might go to 3.10 after 3.9.

From the article above:

> Update: After this post was originally written back in 2014, subsequent discussions on the core python-dev mailing list led to the conclusion that the release after 3.9 will probably just be 3.10. However, a 4.0 will presumably still happen some day, and the premise of this article is expected to hold for that release: it will be held to the same backwards compatibility obligations as a Python 3.X to 3.X+1 update.

Re: Most popular Python packages now support Python 3

#77
post #30

Python 3 is a case study on how you should never create a new version of a language implementation that can't load and interface with code written for the old version. After almost 10 years, the old version is still in use, and the new version isn't even that much better.

I don't know. The introduction of Python 3 caused massive headaches and fractured communities, but the alternative of dealing with unattractive warts in a language until eternity is also not very attractive.

I quite like Python 3, and most of the backward-incompatible changes it introduced.

Re: Most popular Python packages now support Python 3

#78
post #67

Libraries are mostly ported at this point. It's the applications and plugins that still need work. Here's the status in Fedora: http://fedora.portingdb.xyz And history: http://fedora.portingdb.xyz/history/?expand=1

Yes. My friend is employed at Redhat and he told me that he also works on porting 2 to 3 (although not fulltime), and it is a huge amount of work. They work on it several years already, and it is still far from finished.

It's that why the default version of Python on RHEL 7.x is 2.7 instead of 3.x?

Re: Most popular Python packages now support Python 3

#80
post #73

Was it just the time that the ecosystem needed to adapt to the Python 3 changes or were there essential changes in the 3.x versions up to 3.6 that made it easier to switch from Python 2?

Some of both (for example, % formatting got added back to bytes objects in 3.5).

Also, supporting 2.5 (or even 2.4) together with Python 3 was particularly inconvenient, so things sped up after people stopped caring about those (which took a long time because some people were running extended-support enterprise distributions).

Post reply on HN