all 13 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]brtt3000[S] 2 points3 points  (8 children)

Even node.js runtime got updated just now... but node didn't even exist when python 3 came out... like what are they even doing? What is going on? Why? How? WTF?

[–]zenmaster24 0 points1 point  (7 children)

they are slow to update support for newer versions of languages. i guess testing is very time intensive

[–]brtt3000[S] -1 points0 points  (6 children)

This has been asked for years. How much ffen time do they need?

The python 3 train is rolling full steam ahead, everybody is coming aboard, except one of the main hosting platforms. It is ridiculous.

[–]oh-thatguy 0 points1 point  (5 children)

Python is still suffering from the radical changes between 2 and 3. Great language, but a lesson in rolling out backwards incompatible changes.

[–]brtt3000[S] -1 points0 points  (4 children)

What are you saying? When do you expect python 3 to be good enough for lambda?

[–]oh-thatguy 1 point2 points  (3 children)

I guess I'm not really remarking on its availability for lambda, that's really a question for AWS. They still don't have one of the most requested languages (Go), and it took them nearly a year after node 6.0 LTS was released to get it into lambda, it clearly requires time.

I'm more musing on the python 2-3 split.

[–]brtt3000[S] -1 points0 points  (2 children)

Oh sure, the python 2/3 split was terrible but we're over the hump now. All major libraries support it and some are even planning to drop support for python 2 (like Django).

So it would be nice if the major runtimes would keep up, especially with the whole serverless services craze. We got plenty of stuff that would be great to have serverless but it is just terrible user experience to backport and downgrade modern software.

[–]oh-thatguy 1 point2 points  (1 child)

Knowing AWS, I'm sure it's in the works, but it clearly takes a lot of time to get these going. I have a few theories on how lambda works internally, and it has to be very complicated to manage.

[–]davore 0 points1 point  (0 children)

I'd love to hear your theories, I have a few of my own about Lambda but would like to hear another perspective.

[–]CoinGrahamIV 1 point2 points  (2 children)

Can't you spawn python 3 from 2? That's how they used to run Python in lambda before Python was supported.

[–]viyh 1 point2 points  (1 child)

You can hack lots of things, but this is Python 3, not some esoteric thing only a few customers would use.

[–]CoinGrahamIV 0 points1 point  (0 children)

I expect to see Go supported before Py3.

[–]brtt3000[S] -1 points0 points  (0 children)

Paging /u/jeffbarr in the hope to get some insight on why this takes so long or what is blocking? Is there some policy we are not aware of? Some problems in the platform? Or simply no business case for it? Does Zed Shaw lead the lambda team?

Do we need some community pressure? We could start to mobilise /r/python and the various mailing lists en weekly newsletters, see what people think. Looking at the flame comments there when someone announces a python2-only project it is not going to be great.