-
Notifications
You must be signed in to change notification settings - Fork 420
DeprecationWarning for distutils in Python 3.10 (will be removed in Python 3.12) #906
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
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
It will be tricky to support both 3.6 and 3.12 at the same time By the time 3.10 runtime is officially launched, python 3.6 would be deprecated? |
@nayaverdier thanks for raising the issue. Lambda runtime does not support 3.10 yet hence why this hasn't been actioned. |
Would a PR on this be helpful or would it not be considered until 3.10 (or 3.12) is a supported lambda runtime? |
@nayaverdier 3.10 support comes sooner ;) |
I'd love a PR! I would take any help I can get ;-) |
What were you trying to accomplish?
Run tests utilizing aws-lambda-powertools.
Expected Behavior
No DeprecationWarning to appear.
Current Behavior
When running tests (specifically using
pytest
) that importaws_lamdba_powertools
, aDeprecationWarning
appears.Possible Solution
The only function used out of distutils is
strtobool
, and it is only used in one place, so that logic can simply be copied into theresolve_truthy_env_var_choice
function inaws_lambda_powertools.shared.functions
.Steps to Reproduce (for bugs)
python3.10 -m venv .venv
and. .venv/bin/activate
)pip install aws-lambda-powertools pytest
echo "import aws_lambda_powertools" > reproduce.py
pytest reproduce.py
Environment
1.22.0
This warning appears in development workflows, but will be eventually breaking when Python 3.12 is released.
The text was updated successfully, but these errors were encountered: