Pydantic and aws-lambda-powertools[all] #2627
-
Hello, In the project I'm currently working on, we have encountered a persistent issue related to installing packages in virtualenvs within GitHub Actions. This error frequently arises and needs to be addressed:
In the requirements.in file we have the following:
This has been happening once a month, and we're not quite sure how to resolve it. Any suggestion? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
Oi @saomartinho, tudo bom? Could you provide a little more information about this error? I mean what version of poetry/pip are you using. The action you are using... I tried to simulate it here but I couldn't. Thank you. |
Beta Was this translation helpful? Give feedback.
-
Hey! Send us an email - aws-lambda-powertools-feedback at amazon dot com -
and I’ll send you a calendar link so we can troubleshoot this together live
;)
Less guessing work
…On Tue, 25 Jul 2023 at 12:57, São Martinho ***@***.***> wrote:
If we change the setup command from "setup": "pip install -r
requirements-dev.txt && python setup.py develop", to this "setup": "pip
install -e . && pip install -r requirements-dev.txt && python setup.py
develop",. The pipeline pass, do you think is a better solution?
Also i see the new version from aws-lambda-powertools (2.21.0
<https://github.com/aws-powertools/powertools-lambda-python/releases/tag/v2.21.0>)
supports now pydantic 2, do you think this can resolve the problem?
—
Reply to this email directly, view it on GitHub
<#2627 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZPQBCVZCDOVSEACABDOTLXR6RCTANCNFSM6AAAAAAZ4IKD2M>
.
You are receiving this because you were mentioned.Message ID:
<aws-powertools/powertools-lambda-python/repo-discussions/2627/comments/6539106
@github.com>
|
Beta Was this translation helpful? Give feedback.
Opa @saomartinho! I highly suspect is down to two reasons:
requirements.in
and not the latest[all]
here) with hashes.IIRC this can also happen in
pip-tools
when you compile deps in a particular Python version while CI is in another (dependency resolution based on python version, e.g. typing-extensions). Any inexact pinning of one dependency will cause this error message.For now, try:
requirements.in
use an exact version in Powertools:aws-lambda-powertools[all]==2.9.0
--use-deprecated=legacy-resolver
flag with…