Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Most popular Python packages now support Python 3

py3readiness.org

Post reply on HN
Print view View original

121–130 of 166 posts

Re: Most popular Python packages now support Python 3

#121

Post by adeelk93 »

jnbiche wrote: post #69
frou_dh wrote: 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.

The migration is done. Anyone who's not starting projects in Python 3 now will soon be obsolete, because the community has definitely moved on.

Community might have, but industry hasn't. You're right, the dust has settled. If you haven't migrated to Python 3 yet, you likely never will. All the reasons to use 2 or 3 have already been established. I doubt there will be any more new information that will sway people from the stance they've already taken.

Re: Most popular Python packages now support Python 3

#122

Post by Too »

sago wrote: post #8

Clicking around, those that don't seem to be: 1. Obsolete. Either explicitly so (e.g. Google API) or abandoned, without even a minor/patch release (initools, 2010) or in some cases a code commit (e.g. pathtools, 2012) for five years or more. I suspect that they will never be Py3, the community will just move on to alternatives. 2. Working hard to bring support (e.g. ansible). 3. Part of the graphite ecosystem. If the…

5. Has other equally or more cable alternatives in python3. Eg there's no reason to use python-ldap when you have ldap3.

Re: Most popular Python packages now support Python 3

#123

Post by meowface »

frou_dh wrote: 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.

I think the reasonable middleground for most Python devs right now: if a medium or large project already written in Python 2 is working well, you can keep it as is, but new projects should be written in Python 3. That unfortunately isn't an option for many people in corporate and other bureaucratic environments, but when it is an option there's no reason not to do so.

Re: Most popular Python packages now support Python 3

#125

Post by makk »

Cyph0n wrote: post #104
actuallyalys wrote: post #102

Earlier quoted context omitted.

>The language maintainers themselves have clarified that introducing breaking changes was a mistake in hindsight and that it will never happen again. What are you referring to? I haven't heard or read any core developers say anything close to 'introducing breaking changes was a mistake in hindsight'.

I recall reading something along those lines, but I could be mistaken!

100% sure I read that from one of the core devs but cannot find the reference.

Re: Most popular Python packages now support Python 3

#126

Post by adamtulinius »

odonnellryan wrote: post #81
sago wrote: post #8

Clicking around, those that don't seem to be: 1. Obsolete. Either explicitly so (e.g. Google API) or abandoned, without even a minor/patch release (initools, 2010) or in some cases a code commit (e.g. pathtools, 2012) for five years or more. I suspect that they will never be Py3, the community will just move on to alternatives. 2. Working hard to bring support (e.g. ansible). 3. Part of the graphite ecosystem. If the…

Supervisord isn't open source? What

Open source doesn't mean the source must be publicly available for everyone to read. :)

Re: Most popular Python packages now support Python 3

#127

Post by PurpleRamen »

tigershark wrote: post #98
Cyph0n wrote: post #64

Earlier quoted context omitted.

Tedious? How so? Because there is no more Python 2 vs 3 anymore. Whoever hasn't migrated will be stuck using deprecated libraries and outdated tools. Yes, Python 3 was initially a risky endeavor, but in the past couple of years it has cemented its position as the true and only version of Python.

For me, completely outside the Python community, I really can't fathom how migrating to the next major version of the language can protract for so long... And I have been in some painful migrations in my life... Java 1.4 to 5 in a >1M loc "enterprise" application. From an object oriented database to oracle in the same application. But it didn't last for close to 10 years. It's simply a complete nonsense to my eyes.

It's not 10 years, just 2-3 years. Python3 for the longest time was not useable. Only with 3.3 it became stable enough, and it took until 3.5 until it was even good enough and many libs were ported.

On top of it, Python2 works so well and python3 introduces so few advantages that doing an expensive port is just not feasable for many codebases.

And I guess that python is used mostly by smaller companys with constantly lacking manpower and money plays also an important role.

Re: Most popular Python packages now support Python 3

#129

Post by git-pull »

sago wrote: post #8

Clicking around, those that don't seem to be: 1. Obsolete. Either explicitly so (e.g. Google API) or abandoned, without even a minor/patch release (initools, 2010) or in some cases a code commit (e.g. pathtools, 2012) for five years or more. I suspect that they will never be Py3, the community will just move on to alternatives. 2. Working hard to bring support (e.g. ansible). 3. Part of the graphite ecosystem. If the…

In addition, Fabric doesn't support Python 3. The feedback I've gotten back on when Python 3 will be supported and how much of the legacy fabric API's will be supported is even more limited.

There is a fork with Python 3 support: https://github.com/mathiasertl/fabric/

If you use fabtools, I maintain a fork of it for fabric3: https://github.com/develtech/fabtools/tree/fabric3

Re: Most popular Python packages now support Python 3

#130

Post by merb »

striking wrote: post #15
jasonrhaas wrote: post #4

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…

For network glue, Go is a wonderful and super useful language. Not just in how efficient it is, or how easy FFI calls are, but also in how easy it is to deploy. I don't see Go replacing anything that isn't a lightweight server or really small data processing script, though. Anything Tensorflow or numpy of any notable complexity will probably remain Python afaict.

well I wouldn't call kubernetes less complex. and it's still written in go. I think stuff like that is where go shines.
Post reply on HN