You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
Currently, google-resumable-media depends on requests>=2.18. On import, the package checks that this dependency is valid and met. This then checks that all dependencies down the chain are also valid and met.
The issue here is that then a pkg_resources.ContextualVersionConflict is raised when a dependency of requests isn't met when calling the version-check pkg_resources.require('requests >= 2.18.0').
For example, if requests has the requirement urllib3>=1.21,<1.25, but a package further up the chain (eg sentry-sdk) had the requirement urllib3, then the latest version of urllib3 (which is v1.25) will be installed. pip then warns the user that requests requirement won't be met, but in my experience these warnings have not caused issues in the past.
Currently,
google-resumable-mediadepends onrequests>=2.18. On import, the package checks that this dependency is valid and met. This then checks that all dependencies down the chain are also valid and met.The issue here is that then a
pkg_resources.ContextualVersionConflictis raised when a dependency ofrequestsisn't met when calling the version-checkpkg_resources.require('requests >= 2.18.0').For example, if
requestshas the requirementurllib3>=1.21,<1.25, but a package further up the chain (egsentry-sdk) had the requirementurllib3, then the latest version ofurllib3(which is v1.25) will be installed.pipthen warns the user thatrequestsrequirement won't be met, but in my experience these warnings have not caused issues in the past.Four solutions I can think of:
requestsallowurllib3=1.25(see this issue)urllib3<1.25in the applicationrequestsdependency validity at run-timerequestswhen checking for dependency validity at run-time