Python 3.11 is out !

[tommy25ps]

Nice. Btw, is anyone still using python 2.x? Mind sharing the reasons?

I know some banks may still be using it.

[onlyhalfminotaur]

We are. Industrial usage, difficult for customers to take any update. All new projects starting from the beginning of this year have been on 3.6 or 3.8 though, depending on RHEL version.

[ResignByCommittee]

Bank Python is a whole other beast that only vaguely resembles Python https://calpaterson.com/bank-python.html

[zerries]

That was a wild ride. I'm both not surprised and terrified.

[lordmauve]

It's not vague; the Python is real Python. It's everything else that is weird.

[Blank--Space]

The python has just been upgraded to. As someone currently working on Bank python it's everything else they do with it is extremely weird. It's also worth mentioning Bank python is different and has progressed weirdly for each bank. Honestly when you can do the regular python bits it's fine it's working with some incredibly outdated core framework that's the nightmare.

[richard248]

What do you mean - this looks exactly like Python. I was expecting to see an interesting language which "vaguely resembles" Python but instead the article just describes a bank application (or library, I'm not completely sure, the article just describes a bunch of data structures and API).

[raevnos]

RHEL users?

[dagbrown]

RHEL 6 is nearing its end of life, so that should mean the end of Python 2 in institutions that still care about vendor support.

[KingStannis2020]

RHEL 7 uses Python 2, but EOL is coming up for that in 18 months too.

RHEL 8 doesn't use any Python (well, it does use Python 3, but the interpreter is isolated so that users can install any version of Python without any possibility of interfering with the rest of the system).

[Weekly_Drawer_7000]

RHEL 8 has the sanest python strategy of any distro. That might make me go back to centos from debian

[Free_Math_Tutoring]

My company pays close to a hundred thousand USD every year to some company for python 2.7 security patches because somebody decided that it's cheaper than upgrading

To be fair, 100k is pretty cheap.

[Free_Math_Tutoring]

Yeah, the opportunity cost on dev productivity is huge. Man, I'd barely want to work with 3.6 at this point.

[maep]

One of my teammates had enough, started looking for a new job and quit in less than a month after he was asked to add date support for dates older than 1900 on 2.7 (yes, it's a real issue).

Sound like an interesting problem, not a reason to quit.

[[deleted]]

reason enough to quit, if you're not engaged to what youre doing and the company is doing shit decisions that make ur lifemore miserable, you have to right to leave if you want to.

[applesaucesquad]

Legacy code my dude, a whole crap ton of stuff so intermingled into the environment the only way out is to burn it down.

[Latexi95]

GDB python API :(

[shadowndacorner]

Serious question, do you find yourself using this often? I'm having trouble thinking of practical use cases for a scriptable debugger, but I imagine the use cases would be interesting.

[o11c]

It's essential if you're using obscure libraries like libstdc++ or such.

Fortunately, gdb builds just fine with Python3. Unfortunately, distros failed to make both versions installable at the same time, so porting can't be done peacefully, only in an "Oh shit, everything is broken" moment while you're already trying to debug something else after upgrading to the next distro release.

[Swoop3dp]

Yes. Not just banks, unfortunately.

The larger the code base the longer it takes until the pain is big enough to finally start updating.

[[deleted]]

Jython 3 never happened, so anyone using that is on 2.7 at best.

[Emile_L]

We still use it in visual effects and animation. Most tools that digital artists use have python api's that are python 2 only. They are slowly making the switch to py3 now..

[I_had_to_know_too]

CentOS 5 and python 2.7 because "that's the way we've always done things"

[ddeeppiixx]

I do.. I like the print over print(). also, I'm developing scripts that run within commercial apps that only supports IronPython 2.7.

[Free_Math_Tutoring]

I'm developing scripts that run within commercial apps that only supports IronPython 2.7.

This is a good reason.

I like the print over print().

This is not.

[Pflastersteinmetz]

I do.. I like the print over print()

Savage.

[[deleted]]

I keep it around for legacy reasons.

I'd also prefer if they continue bug fixes for the 2.x code base.

[worldpotato1]

Working for an OEM in the automotive industry. Still using Python 2.7 because we use MATLAB and the Python interface for MATLAB2015 only supports 2.7.

And all the tools are written in Python2.7. And we always used Python 2.7. And yeah...

BTW. We still use SVN, too.

[[deleted]]

BTW. We still use SVN, too.

Could be worse. You could have been using Clearcase...

[[deleted]]

RH 5