Consider updating restrictive max-version dependencies (e.g. six, future, requests)

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave “+1” or “me too” comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Tell us about your request

I constantly struggle with keeping my requirements file free of dependency conflicts due to some of the version requirements imposed by awsebcli, namely six, requests and future seem to be the biggest offenders.

awsebcli v3.18.1 requires:

• future>=0.16.0,<0.17.0
  • future v0.17.0 was released October 2018
• requests>=2.20.1,<2.21
  • requests v2.21.0 was released December 2018
• six>=1.11.0,<1.12.0
  • six v1.12.0 was released December 2018

One workaround is just to have a separate environment for using awsebcli, but it would be great to get everything working in one env.

I don’t know the history/details behind these restrictions, but I would think/hope that they can be improved at least somewhat.

[SafaAlfulaij]

Can we please update pathspec version? It’s causing issues with black for almost a year now…

There are incompatible versions in the resolved dependencies:
  pathspec<1,>=0.9.0 (from black==21.10b0->-r C:\Users\User~1\AppData\Local\Temp\pipenvt585eh4arequirements\pipenv-inunr0b_-constraints.txt (line 8))
  pathspec==0.5.9 (from awsebcli==3.20.2->-r C:\Users\User~1\AppData\Local\Temp\pipenvt585eh4arequirements\pipenv-inunr0b_-constraints.txt (line 5))

[simoroma]

I still have the same issue with awscli 3.19.3 when I install s3fs: awsebcli 3.19.2 requires botocore<1.20.0,>=1.19.0, but you have botocore 1.17.44 which is incompatible.