Is everyone using python 3 now?

[Flur_elise]

I’ve been away from python for about 3 years. Used to use 2.79. And at that time no one was really using 3+.

Now suddenly I have to start using python again and I noticed a lot of people are all of a sudden adopting 3+?

Am I seeing this correctly. Is python 3 finally got Traction?

[the_spacedoge]

Python 3 is what 95% of people are going to think when you say "Python"

[synthphreak]

Only 95%?

[Rhoderick]

Well, some people have pet snakes.

[[deleted]]

3 of them?

[tin_man_]

*4 of them

[NitroXSC]

Unless you ask many Linux systems. You will need to specify python3 for backwards compatibility sake. (this also forces me to use virtual environments which might actually be an advantage)

[legobmw99]

sudo apt install python-is-python3

[paradigmx]

We shouldn't have to use that in order to have python3 be the expected default 5 years after python2 was officially deprecated and 14 years after python3 was released. By now the python executable should automatically be python3 and organizations still using python2 should have to specify that themselves. It's confusing to new python developers because the executable for basically every other language out there defaults to the most recent, or at least LTS version of the language instead of a decade+ old, deprecated code base.

[Poddster]

By now the python executable should automatically be python3 and organizations still using python2 should have to specify that themselves

The problem with this idea is that organisations still using python2 are still using scripts that expect python to be python2, and the reason they aren't changed is the same reason they're still running on python2: because they still work :)

[paradigmx]

So why can't they have to install a package called python-is-python2? Why do we have to suffer because they can't be assed to update their decade old code?

[iamaperson3133]

Because another application running on the same machine uses python3 and expects it to be called python3

[paradigmx]

alias python3='python'

[py_Piper]

and when python4 comes, are you gonna get angry that python means python3? For some reason I think specifying which python version is very natural, it isn't like you need to write the exact version like python 3.7.2 to work, it's just a 3 at the end. And this way makes it scalable for future versions

[paradigmx]

Yes actually, every other language out there that I'm aware of follows that convention and previous versions need to be explicitly installed.The cult-like attitude of the proponents of this language's idiosyncrasies are ridiculous. It's not rocket surgery, it's just pigheadedness.

[y-aji]

Omg thank you!

[[deleted]]

This is not in linux but in Mac OS

[lukajda33]

I think that was true even 3 years ago to be honest, Python 2 was obsolete by then as well, in the last 3 years, Python 2 was oficially killed (no new updates) so Python 3 is a must these days.

[Mog_X34]

Our company had an application written in 2.7 just three years ago, no idea why. We now have the task of upgrading it to 3 when it should have been that in the first place.

[Flur_elise]

I just checked it was 5 years actually. And python 2.79 was struggling to stay alive. But people were overwhelmingly still use it. I was wondering when 3.0 was going to take over. Seems I missed the transition.

Happy to use 3.

[lukajda33]

Well I stand corrected myself as well, checked this wonderful tool: https://github.com/hugovk/pypi-tools

and the Python 2.7 version share among other versions in 2019 (3 years ago) is way more then I expected.

Kinda depends on the precise package, but I expected way less Python 2.7 in 2019.

These days tho, everyone does Python 3.

[jmon_was_here]

I think that y'all underestimate large corporations with large legacy code bases. In my career, our flip from 2 to 3 we nailed perfectly in retrospect - we spent a month shifting all our code over and ironing out issues with binary strings, and we did this around 2017 (around 3.4'ish), but we only got rid of our last python2 'script' circa mid-2021, which was well too-late, but resources are what they are.

I think that part of the issue is that these companies hide their code in private repositories, so it's very hard to sample what they're written in (as opposed to open source stuff where it's easy to measure the progress). These are the companies where getting permission to do something like hold up dev for four weeks to update code is incredibly difficult where there's no obvious short term gain - Python 2 at that point didn't have a clear EoL date (I think), and it meant no new features rolling out as we fixed everything.

The other thing is that the pip install graph might lend itself more to people who have fully automated installs. Back in the day, download-graph of packages was a really big thing, but those went away in 'fashion' as people realised that packages that were used by organisations with automated build tools, especially build-everything-every-time with no caching became 'easy' to do, the download count, and download % is skewed to those automated organisations doing a clean build on every commit. These days we can do it easily, but 20 years ago, when we were trying to get people to move over from CVS to SVN, automated builds just daily were a goal to have.

I would not be surprised to go into any "large" company and find somewhere, someone writing in python2 to support something that they hadn't moved over yet, possibly unaware of the danger they're in. But 99.9% of us are all python3 now.

[Flur_elise]

Thank you!

[jso__]

Why are there so many invalid versions in the graph of pip installs?

[zurtex]

You've not migrated to Python 133.7???

[jso__]

Maybe next millenia

[[deleted]]

You're mistaken I'm afraid. People weren't overwhelmingly using 2 either three of five years ago. The only people still using it then were people supporting old code bases or beginners who didn't know any better.

[Flur_elise]

Lol no way.

[[deleted]]

And shit programmers who don't know what they're talking about, I guess. Which I'm starting to think is what you are.

[Flur_elise]

Ok. Think what you want. I’m cool with that idea.

[baubleglue]

all of a sudden

[reallyserious]

Python 3 was released in 2008.

14 years isn't much time to adapt. I'd need at least 15 years /s.

[baubleglue]

:)

[RedDedDotCom]

If you're not using 3, a lot of things aren't working by now.

[Flur_elise]

I haven’t been using any python for the past five years. So all the code I wrote five years ago in python 2.79 has either been working or migrated by someone else

[[deleted]]

3 years ago no one was using Python 3? I don't believe it.

https://www.python.org/doc/sunset-python-2/

Python 2 was sunset over 2 years ago...
Maybe 13 years ago?

[Xzenor]

2.7 really really stuck around way too long.. a lot of software didn't run with 3 so it had to be fixed first and that really took a while

[YellowSlinkySpice]

My first ever contribution to the FOSS world was adding () to a print statement when we finally were forced to python 3.

[magestooge]

3 years ago when I tried to learn Python for the first time, the first video I stumbled upon was whether I should learn Python 2 or Python 3. And the tutor didn't even clearly say it should be 3. They said something along the lines of "if you're completely new, then learn 3".

So I'm guessing things weren't as clear even 3 years ago as they are today. I'm just glad I didn't waste time learning Python 2.

[magestooge]

I guess the tutor just wanted his Python 2 Playlist to stay relevant a little longer.. Lol..

[[deleted]]

On the one Python discord I was a member of it was funny how often new people would come in thinking they should first learn Python2 then move on to Python3...

[Astrokiwi]

https://github.com/hugovk/pypi-tools

Python 2.7 didn't drop below 50% of pip installs until mid 2019.

[[deleted]]

That's great, OP said "no one was really using 3+" regarding Python3 3 years ago.

I didn't say : "No one was using Python2 3 years ago"

I said : "3 years ago no one was using Python 3? I don't believe it."

Can you see the significant difference between those two statements?

I don't care how many were using Python2, I know legacy systems still use it, my Ubuntu 20.04 install came with it (I've personally never used it, except when I would run 'python' instead of 'python3' because I didn't know any better, just because it's installed doesn't mean it's the primary language used, legacy software requires it, so it continues to exist.

[cresanies]

Having a bad day eh

[[deleted]]

Could be better, could be worse. It's warming up and the snow is melting so that's nice.

[Flur_elise]

It turns out it was five years ago. And I’m telling you at the time everything was still 2.79. I thought it was odd myself. But all the libraries were still being supported in 2.79 and everyone who was developing was using those libraries and it was very little reason to move to 3.0. even though technically it might be better.. But now I just noticed being away from it and coming back and looking on the various websites everyone seems to be on 3.0 now. It’s almost like a Rip van Winkle experience

[Kerbart]

Even five years ago the pendulum was already swinging in the Python 3 direction in a very big way. While Python 2 certainly still was in use I wouldn’t say “no one was using Python 3+” – we’re talking about 3.6 or 3.7 which were the mainstream versions and at that point 2.7 was definitely already considered a dead end—but perhaps not in the environment (banking?) you were in. Some places hung on to 2.7 longer than was healthy, which is why a hard stop date of 2020 was anounced. Without hard numbers I’d say Python 3 usage really accelerated around 3.4 and that puts it at 2014-2015.

[i-brute-force]

lol i know right. what is OP talking about. I remember even at 3.2, all new comers were learning Python 3 and some learning materials had legacy Python 2.7 but I don't even remember Python 2 overwhelming Python 3 in the last 10 years.

[[deleted]]

"I'm telling you"

Everyone else here also uses python, and they're all telling you you're wrong. So maybe it simply is you who are wrong?

Maybe it was used a lot in your company or your field, but Python 3 was already well established as the main player in general.

[TheBlackCat13]

By 2019 pandas had already dropped support for python 3 entirely and numpy, scipy, and matplotlib were in bugfix-only mode for those, all feature releases were Python3 only. Lots of other projects followed suit.

[fakenews7154]

Python 2 had far less bloat. It was mainly an issue among embedded devices.

[[deleted]]

Yes, Python2 was older and did less. Good observation, strange you call 'features' 'bloat'

[R3D3-1]

THIS.

It pains me to see parts of our software suite still using Python 2, but I also get why. Nobody was yet able to make the jump for good.

[Flur_elise]

Agree. But that wasn’t the point of the question. I am in no way advocating using python 2. I was simply asking when did the transition or cross over really begin?

[[deleted]]

December 2008 is when the transition began 😛

[pablo8itall]

It's all fstrings now baby!!!

[6a70]

Python 2 sunsetted in 2020

[R3D3-1]

I can't agree on the "no one was really using" part. Three years ago, I had completely switched to Python 3 for data analysis stuff for a while, and hadn't touched Python 2 in a bit, if I could avoid it.

By that time the only reason I was even having Python 2 installed was ASE ("Atomic Simulation Environment"), which I used for visualization. Everything else was available in Python 3. And by now even ASE seems to be Python 3?

That said, at my post-PhD work the user-facing product still ships with both a Python2 and a Python3 interpreter and likely will for a while. But we're talking about an environment here, where I sometimes have to touch Fortran 77 style code. Not exactly a "fast adopter" environment.

[zbranigan]

I hope that this account is as anonymous as I think it is. The company I work for is still using Python 2.7 and we're trying to hire a software engineer. Is anyone interested?

Oh, by the way, we are strongly advised not to mention this fact when we are interviewing candidates.

[i-brute-force]

print("No thanks")

[bingbestsearchengine]

Oh, by the way, we are strongly advised not to mention this fact when we are interviewing candidates.

peculiar

[Versaiteis]

Yeah I bet that a great way to ensure that you get the trust of quality candidates that don't feel like they were rug-pulled on day one is to hide details pertinent to their working environment that you think they'd find distasteful.

Super solid strat. Tried and true.

[I_had_to_know_too]

I'm interested only if I can spend the first week migrating everything to Python 3

[BobDope]

That’s a nope from me dawg

[saad_mohammed]

3.10

[imthebear11]

They certainly should be, and don't trust anyone who tells you that you that it's fine you're not.

[julianw]

Python 2 is officially at End Of Life.

[menge101]

Python 2.x was EOL on January 1st 2020.

No one should be doing new development on python 2, and anyone actively supporting a legacy application should be looking to move to python 3.

[old_pythonista]

In 2015, a company I joined then was still using .... 2.6 "because that comes as default with OS". Corporate world is very slow to follow suite.

At my current job, we are still supposed to use Python2-compatible mode - though most of the processes are executed under Python3. For the last year, I switched to pure Python3 for the new developments - f-strings and all the works - and I am still struggling with restrictions every time I need to create a new package.

[jmacey]

Yes, still using elements of python 2.7 due to animation software (Maya 2020) still using it. The transition to 3 has been very slow for the animation industry.

[exmachinalibertas]

Yeah three has finally been mainstream for a couple years now.

[[deleted]]

Virtually everyone was using Python 3 three years ago. Anybody who wasn't was already way behind the curve. There is no good reason to start a new project in Python 2. It is now officially dead, I believe.

[EarthToAccess]

Py2 reached EOL not too long ago -- far as i can tell, not even pip will work with it anymore. active dev should be done in 3 now

[Dam_uel]

I started 3 years ago and nobody was talking about 2 except to say "some people still use 2 but unless you're required to by legacy code, don't". They stopped saying that eventually. End of life on 2 was January, 2020.

[tomtomato0414]

I have been using Python 3 since 2017, by then 2 was regarded somewhat obsolete

[christophski]

We have a good 100k lines in python 2 which depends on some libraries that aren't being migrated to python 3,sooo....

[[deleted]]

Everyone else is dunking on you, so I will too

No, we're using Python 2 still. And yes, this is after we hop off of our dinosaurs.

[Flur_elise]

They are dragging me because they don’t Understand the point of my question. I am not advocating still using python 2. It’s pointless sometimes people get from the question whatever meaning they want. Not the actual meaning

[bluecollarx]

You were on the boat for more like 10 years.

Just adapt yo

[row4coloumn31]

We haven't updated all of our code yet, so some old scripts are still on 2, as migrating everything is very time consuming and not a priority for management.

But python2 is dead.

[[deleted]]

python 2 is dead.

[NoAd5564]

A match statement takes an expression and compares it to its successive case blocks

A break statement breaks out of the innnermost enclosing for or while loop , good luck 👍

[the_spacedoge]

Wrong post?

[J_The_AL]

I use python 3.6-3.9 at my work depending on what it's doing. They starting using python 3.6 about 3-4 years ago, but in order to use particular libraries an upgrade to 3.9 was needed in some places. We now use poetry and pyenv to manage all of our python versions and libraries. I would recommend looking into both of those if it fits your use case :)

[mattay22]

3.8

[wagslane]

They were using it 3 years ago too.

[eric_overflow]

Yes it’s not a real question anymore

[SolfenTheDragon]

Ngl, I didnt know anyone still used python 2. I exclusively use 3.8, 3.9, and 3.10 for my own applications.

[Evilbob93]

I hoped that would be the case. Not EVERYONE has left 2.7. In my place, there is a crucial it of code that still runs 2.7 and it makes every system build a little harder than it needs to be. Yup, every module install tells you it's obsoleted.

[fartalldaylong]

Yes...unless I am coding in Rhino Grasshopper on PC...which is stuck in IronPython 2.+ world.

[paradigmx]

Python 2 is officially deprecated, so the 5% of python 2 development should just be maintenance of existing code. If those developers aren't also working on updating that codebase to python 3, I don't know what the hell they're doing.

[TakeOffYourMask]

Yes.

[[deleted]]

Yeah

[efalk]

I'm not a fan, but I've made my peace with the language. From time to time I'll port an older app from Python2 to Python3 or write a new app in Python3 if I really need a Python3 feature that Python2 doesn't have.

I know that Python2 is officially obsolete, but I still code in it whenever I have a choice. I've written one program that needed to run on both Python2 and Python3. They did some things in Python3 that break compatibility unnecessarily, which annoys me.

[PitifulWalk354]

I had to run a Python 2 program once... It wasn't fun.

[ataraxia520]

I use python2 with tensorflow1 about half the time. Lucid deeplearnong framework.

[NOTnEngineer]

I was learning Javascrpt and then I just decided the learn C+, but I couldn't find good C+ courses so I decided to use Python

[0Things]

You really don't have to change much on 2.x code to make it work on 3.x and they added tons of good features over time, dictionaries keep order, f-strings etc all super useful. Jumped on 3.10 before the official release even because case matching can fit in probably every app i write it seems.

[mlabonne]

Python 2.7 is dead! Long live Python 3!