Hacker News Reader

Comment by icebraining | Hacker News Reader

Python? Good luck. Every frigging month (practically) it's a breaking change. You have to work furiously just to keep your infrastructure working, or purposefully draw a line in the sand (2.7!).

What? There was exactly one breaking point, from Python 2 to Python 3. Which "monthly breaking changes" are you talking about?

View on HN

Probably not the language itself, but the quivering mass of libraries with moving APIs and bolted-on design fads. Numerics is numerics--functions, matrices, linear algebra and indexing isn't going to change any time soon.

That Fortran gets bashed and Lisp is worshiped seems quite incongruous.

I'm not a Python developer but what I've seen and find frustrating is the slow migration of libraries to Python 3. Some projects have switched to 3 and some are sticking with 2 for now. Some applications are using 2 because they have dependencies using 2, but as those dependencies switch applications have to deal with combining Python 2 and Python 3 dependencies.

I know each issue is easy in isolation, but we're talking about old 25M line codebases here. If such things exist in Python it can be a maintenance problem.

I'm in favor of languages making breaking changes occasionally but there is something to be said for languages like Java or Fortran that are intended to keep compatibility forever.

"There was exactly one breaking point, from Python 2 to Python 3"

One breaking point?

The majority of the libraries that I use don't even work properly in Python 3. The standard Mysql library for instance, which is used in the majority of ORMs (including SQLalchemy) isn't included in Python 3, which means you need to make major changes/try to use a different library.

The case of many standard libraries were changed, breaking lots of code. Example: ConfigParser to configparser.

Even simple things like print 'test' is now print('test')

These are only a few examples. There are lots of other major changes that break 2.X code.

I have been using Python 2.X for all of my projects and wanted so badly to change to 3.x for my new projects. However, because of all incompatibilities, I can't.

I don't think I'm alone on this either. Python 3.X still isn't being used by the majority of developers.

Posting this censored comment for the good of the community; it seems entirely reasonable, although a bit overwrought.

"Gurer jnf rknpgyl bar oernxvat cbvag, sebz Clguba 2 gb Clguba 3"

Bar oernxvat cbvag?

Gur znwbevgl bs gur yvoenevrf gung V hfr qba'g rira jbex cebcreyl va Clguba 3. Gur fgnaqneq Zlfdy yvoenel sbe vafgnapr, juvpu vf hfrq va gur znwbevgl bs BEZf (vapyhqvat FDYnypurzl) vfa'g vapyhqrq va Clguba 3, juvpu zrnaf lbh arrq gb znxr znwbe punatrf/gel gb hfr n qvssrerag yvoenel.

Gur pnfr bs znal fgnaqneq yvoenevrf jrer punatrq, oernxvat ybgf bs pbqr. Rknzcyr: PbasvtCnefre gb pbasvtcnefre.

Rira fvzcyr guvatf yvxr cevag 'grfg' vf abj cevag('grfg')

Gurfr ner bayl n srj rknzcyrf. Gurer ner ybgf bs bgure znwbe punatrf gung oernx 2.K pbqr.

V unir orra hfvat Clguba 2.K sbe nyy bs zl cebwrpgf naq jnagrq fb onqyl gb punatr gb 3.k sbe zl arj cebwrpgf. Ubjrire, orpnhfr bs nyy vapbzcngvovyvgvrf, V pna'g.

V qba'g guvax V'z nybar ba guvf rvgure. Clguba 3.K fgvyy vfa'g orvat hfrq ol gur znwbevgl bs qrirybcref.

None of that contradicts the assertion that Python's only breaking point is Python 2 -> 3.

Is there some reason you ROT13'd it?

No, none of it does.

I rot13ed it in case there's a dead-comment-reposting-killing algorithm on the loose.

Reply on news.ycombinator.com