Why is colorama pinned to 0.4.5? #8571
Assignees
Labels
dependencies
This issue is a problem in a dependency.
investigating
This issue is being investigated and/or work is in progress to resolve the issue.
p2
This is a standard priority issue
source-distribution
cli v2 source distritbution related issues
Comments
Lawouach
added
needs-triage
RyanFitzSimmonsAK
added
investigating
|
Hi @Lawouach, thanks for your patience. I assume you're referring specifically to the AWS CLI v1 pin, since v2 has a higher pin already. If you're able to upgrade to CLI v2, that should allow you to use the higher colorama version. Dependencies for v1 and v2 are tracked separately, we do have an open PR for this dependency. I've asked the team to take a look at the colorama pin the next time they review dependencies. In the meantime, as we have a general tracking issue for dependency pins, I'm going to close this as a duplicate. |
|
This issue is now closed. Comments on closed issues are hard for our team to see. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
Currently, the colorama dependency is pinned to
colorama>=0.2.5,<0.4.5. Is there a particular reason as this means we cannot upgrade some other packages that expect 0.4.6Additional Information/Context
No response
CLI version used
latest
Environment details (OS name and version, etc.)
linux
The text was updated successfully, but these errors were encountered: