Helder Eijs
Helder Eijs
Now in v3.21.0
Dependencies should be included in a Lambda zip file using pip as explained here: https://docs.aws.amazon.com/lambda/latest/dg/python-package.html . Have you tried that?
Your problem (as indicated by the `invalid ELF header` message) is that you are building your lambda on an architecture which is not compatible with the runtime of the lambda....
Sorry, we cannot add a dependency on a library we don't control or that may not be present.
Thanks for reporting. This is fixed with 760cbd53b8cade7c7ed5a4f698d48cc5d508210f
Now in v3.21.0
Thanks for flagging. Master now builds correctly with 3.13-nogil, because py-limited-api is set dynamically and disabled for 3.13-nogil (even if I think support for multiple ABI levels should be sorted...
Thanks, but this was fixed in a more generic way in v3.22
What is the reason for doing so?
Indeed, as with any other open source library, the best option is to download the code, inspect and build it yourself on machines you trust. If you download the code...