Hacker News Reader

Comment by ec109685 | Hacker News Reader

Honest question, why does it matter what version of python lambda supports (or any framework / language for that matter)?

Couldn’t you just pick the go runtime for example and have it execute the framework / language you want with minimal overhead given it will be a call between two processes running on same host, which you can keep running between invocations.

View on HN

AWS just released a solution to run any programming language on AWS Lambda: https://aws.amazon.com/blogs/aws/new-for-aws-lambda-use-any-...

Ok, so I take from this that the post about specifically Python 3.7 doesn't make much sense really (as a HN post).

AWS provides the Python 3.7 runtime for you, so you don't need to bundle it. The post refers to runtimes that AWS doesn't provide, such as Haskell.

It makes sense because this is an AWS supplied executable, where you just upload the .py files.

If you follow the "Run any language" approach, you need to bundle the python interpreter and any libraries required.

> why does it matter what version of python lambda supports (or any framework / language for that matter)?

Python 3.7 is a lot faster (30 - 40%) than Python 3.6 for certain types of functions.

And you can't (easily) just install Python 3.7 from another runtime, because it has a ton of dependencies and takes minutes to compile. So even if it's technically possible, it precludes a lot of use cases.

I actually dealt with a similar problem a couple years ago, we were trying to get numpy on Lambda but there's C compilation that needs to happen. What I ended up doing was provisioning an EC2 instance with the same settings as the environment that Lambda uses, then building everything there, and shoving the binaries in the Lambda. It worked, I'm pretty sure the same thing would work for building Python.

Reply on news.ycombinator.com