-
-
Notifications
You must be signed in to change notification settings - Fork 432
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
Specify more recent awscli dependency to avoid dependency resolution issues #239
Comments
Does this have any side effects, e.g., the more recent awscli version having dependency conflicts with NP? |
Not I know of. |
Could you pinpoint me to where the awscli requirements comes from? I dont see it in the project files. |
Looks like this was removed a while ago. 14d0a20 |
alright, thanks for the info |
though, im wondering, why you ran into this issue. you opened the bug report in 2023 whereas the awscli was already removed in 2022. is this somehow still an issue or you just used an older version? |
Yeah, I believe that's the problem. Although that commit is older than my issue report, the latest version available on PyPi at the time was 1.5.22, which is from 4 April 2022 (18 days before that commit). The first version to include the fix must be 1.5.33, which is from 17 April 2023, about a year later. |
Alright, thanks for the clarification!! |
Mandatory
Related issues:
Describe the bug
news-please depends on
awscli>=1.11.117
, but versions this old have broken metadata on PyPi. Using a package manager that tries to resolve dependencies (such as Poetry) will therefore have to download and inspect every single awscli version that has been published since about 2017. My lastpoetry lock
took 3.5 hours. This issue can be fixed by simply depending on a more recent version (no earlier than October 2021, see aws/aws-cli#5701).I would suggest to simply depend on the most recent at the time, i.e.,
awscli>=1.27.78
.The text was updated successfully, but these errors were encountered: