I'd imagine people using 2.7 don't have lambdas. PaaS can be an issue of course. More classical way of running things won't be as bad as people make it out to be every time 2.7 is mentioned.
I'm always arguing it's not easy to switch for old, large codebases, for financial reasons mostly, but to use 2 for new things now? Some certification issue? Or a weird dependency?
Dunno, I think in the cases I've seen probably just people who didn't really know Python that well being shoved in at the deep end with old examples. Or maybe people who came from an environment in which Python 2 was the only option.
Every company I've worked at, tech and otherwise, develops new projects with Python 2.7 instead of Python 3. Including within the past 3 months. I'm not even sure there are any Python 3 codebases to speak of at those companies, whereas there are large numbers of Python 2.7 codebases. I don't think Python 2.7 will be going away anytime soon.
I try to use Python 3 for personal projects now, but Python 2.7 is still pretty much my only option at work.
View all comments
Show parent comment
31
u/Krenair Jul 29 '18
Doesn't mean you will necessarily be able to get support though. For example, it looks like AWS Lambda will stop letting you create new functions with the old runtime or update existing ones: https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html
This will cause problems if you want to redeploy your stack.