feat: Drop py3.7

[astuyve]

…e ago

What does this PR do?

Python 3.7 is now in phase 1 deprecation, so we do not plan on releasing new features or fixes as there is no continued security or technical support from AWS, and we cannot create new 3.7 functions.

Motivation

Testing Guidelines

Additional Notes

Types of Changes

• Bug fix
• New feature
• Breaking change
• Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

• This PR's description is comprehensive
• This PR contains breaking changes that are documented in the description
• This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
• This PR impacts documentation, and it has been updated (or a ticket has been logged)
• This PR's changes are covered by the automated tests
• This PR collects user input/sensitive content into Datadog
• This PR passes the integration tests (ask a Datadog member to run the tests)

[duncanista]

Looks good, nit:

datadog-lambda-python/datadog_lambda/cold_start.py

Line 149 in 8e74ac2

if version_info >= (3, 7): # current implementation only support version > 3.7

Do we need too change something here?

[duncanista]

Another nit:

datadog-lambda-python/CONTRIBUTING.md

Line 27 in 8e74ac2

# Example: VERSION=1 REGIONS=us-east-1 LAYERS=Datadog-Python37 ./scripts/publish_layers.sh

Maybe we can change this too?

[duncanista]

LGTM!

[astuyve]

Looks good, nit:

datadog-lambda-python/datadog_lambda/cold_start.py

Line 149 in 8e74ac2

if version_info >= (3, 7): # current implementation only support version > 3.7

Do we need too change something here?

I debated this. With the poetry changes, users shouldn't be able to manually include this library in py3.7 functions so it's probably fine. Will remove