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
This isn't a bug per-say, but pytz is pinned to < 2022. This means that I can't use pyuploadcare alongside my code library if I want pytz >= 2022.
The conflict is caused by:
The user requested pytz==2022.2
pyuploadcare 3.0.0 depends on pytz<2022.0 and >=2021.1
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
Expected behavior
The pyuploadcare library should work with later pytz versions as well, so that we can have up to date timezone definitions even if pyuploadcare hasn't needed a release in a while.
The text was updated successfully, but these errors were encountered:
Describe the bug
This isn't a bug per-say, but
pytz
is pinned to< 2022
. This means that I can't usepyuploadcare
alongside my code library if I wantpytz >= 2022
.Expected behavior
The
pyuploadcare
library should work with laterpytz
versions as well, so that we can have up to date timezone definitions even ifpyuploadcare
hasn't needed a release in a while.The text was updated successfully, but these errors were encountered: