Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make boto3 an "extra" requirement #35

Closed
DrGFreeman opened this issue Mar 16, 2021 · 0 comments · Fixed by #36
Closed

Make boto3 an "extra" requirement #35

DrGFreeman opened this issue Mar 16, 2021 · 0 comments · Fixed by #36

Comments

@DrGFreeman
Copy link
Owner

boto3 is currently defined in the install_requires parameter of setup in setup.py. This result in the boto3 and botocore packages being added to lambda layers built using AWS SAM tools. These two packages use about 60 MB of layer storage space, a significant fraction of the AWS lambda layer size limit of 250 MB, although they are not required to be installed in the lambda layer since they are included in the lambda runtime environment.

Moving boto3 to the extras_require parameter of the setup function would prevent the addition of boto3 and botocore to lambda layers while allowing their installation using the 'boto' extra option.

Update Installation section of README and docs to reflect the changes in installation options.

DrGFreeman added a commit that referenced this issue Mar 19, 2021
Set boto3 as optional requirement to avoid unnecessary installation when
building lamda layers.

Remove package dependencies from requirements-dev.txt and install
pacakge them via tox deps parameter.

Update installation section of README and docs to reflect the new
"extra".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant