-
Notifications
You must be signed in to change notification settings - Fork 313
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
Remove hard dependency on urllib3>2 #1382
Comments
We will see how this can be done @alanvgreen |
Agree with @alanvgreen this can lead to
due to the v2 breaking change |
@dhilazo any solutions to fix this issue? Thanks! |
@suyuchenxm if you are referring to the The bugfix |
7.2.1 will stay as is, move to v7.2.2 if you can if not stay at v7.2.0 - until a different workaround is found. You simply have conflicting dependency using two different SDKs for the same work. You could use a custom namespaced deployment where you are using virtualenv. There are various workarounds. |
I upgraded all the dependencies successfully, and everything checks out fine and works without anything breaking.
Both of them work fine along with urllib2.0 upgraded dependency. |
Please check PR #1384 solves your problem. |
@balamurugana when can we expect a release with this fix? |
Removed hard dependency with v7.2.3 |
It would be very helpful if one of anehx's suggestions in #1378 could be implemented, allowing either a later version of urllib3 1.x.x or urllib3 2 to be used.
botocore3 - a package that many minio users would have installed simultaneously with minio - has the requirement
'urllib3>=1.25.4,<2.1 ; python_version >= "3.10"'
. minio is obviously not the first project to encounter versioning drama due to urllib3's v1 vs v2 changes.For our organisation, mandating urllib3>2 at this point is difficult. There are many unfortunate first and third party dependencies and a surprising number of conda environments that need to be updated to use urllib3, and we are only part way through the process. Happy to discuss the situation further, but I don't believe we are unique in finding version pinning issues time consuming to deal with. It wouldn't surprise me to learn that, across all of minio's users, adding the requirement of urllib3>2 caused a thousand hours' unscheduled work.
Implementing a softer transition from urllib3 v1 to v2 will make it easier to upgrade our other package dependencies on urllib3.
The text was updated successfully, but these errors were encountered: