Lambpack
Creates Python 2.7 packages for AWS Lambda, installing requirements and setting build-time variables.
Bare minimum
Lambpack’s purposely minimal - it only packages functions. No uploading, no publishing, no aspirations to become a framework.
Command-line example
Given a directory my-function containing:
index.py with a handler(event, context) function.
An optional requirements.txt listing required packages.
Run the following to get packaged.zip, ready for upload to AWS Lambda:
$ pip install lambpack
$ lambpack my-function packaged.zip index.handler --env DEBUG=yes --env MY_OTHER_FLAG=123
Your function can access the --env variables via os.environ.
API example
As above, but via the API:
import lambpack
lambpack.to_zip(
path="my-function",
dest="packaged.zip",
handler="index.handler",
env={
"ENV": "prod"
}
)
See src/lambpack/packager.py for more info.
Metadata
Release files for lambpack 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lambpack-0.1.1.tar.gz | 4.6 kB | Details |
Release files / lambpack-0.1.1.tar.gz
| Download URL | lambpack-0.1.1.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eaa30fa4eb7381e6c0ccfda3c3048f5aad55c38e3605ad3a4b422310b5e44d86
|
|
BLAKE2b-256 checksum How to use checksums |
05d8b951dff70885161fa1083df5c5ed999666e8b1d5d01cc3f71b31c0393d28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |