Skip to content

Conversation

@deronnax
Copy link

@deronnax deronnax commented Apr 7, 2025

On our project, aws-lambda-typing block the usage of uncapped python version, like requires-python >=3.12:

➜ poetry lock
Updating dependencies
Resolving dependencies... (1.7s)

The current project's supported Python range (>=3.12) is not compatible with some of the required packages Python requirement:
  - aws-lambda-typing requires Python <4.0,>=3.6, so it will not be satisfied for Python >=4.0

Because no versions of aws-lambda-typing match >2.20.0,<2.21.0
 and aws-lambda-typing (2.20.0) requires Python <4.0,>=3.6, aws-lambda-typing is forbidden.
So, because non-package-mode depends on aws-lambda-typing (~=2.20.0), version solving failed.

As a library, aws-lambda-typing should impose restriction on the "max" python usable version (see this Poetry FAQ entry saying libraries should use defines upper bound).

I removed the upper bound and ran poetry lock --no-update with Poetry 1.3 (it seems to be what the project used). I had a result which is slightly different than yours (yours is missing package listing and hash in the lock, that's surprising), but I think overall it should be OK.

I am available if you need more informations.
Cheers

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 this pull request may close these issues.

1 participant