Weird conflict between typing-extensions 4.12.1, xarray, dirty_equals on Python 3.8 #425
Comments
|
We fixed this in 53bcdde... @JelleZijlstra, maybe we should do a patch release? (Do I have the power to do that now? I didn't with the old workflow, but maybe I can after 63d8277... If so, I'm happy to do it.) |
|
Yes, you should be able to do a patch release, go ahead! |
Merged
soxofaan
added a commit
to Open-EO/openeo-python-driver
that referenced
this issue
Jun 18, 2024
Problem should now be resolved with recent 4.12.2 release refs: eu-cdse/openeo-cdse-infra#161, python/typing_extensions#425
soxofaan
added a commit
to Open-EO/openeo-geopyspark-driver
that referenced
this issue
Jun 18, 2024
Problem should now be resolved with recent 4.12.2 release refs: eu-cdse/openeo-cdse-infra#161, python/typing_extensions#425
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FYI: I just created this ticket samuelcolvin/dirty-equals#99 against the dirty-equals project about weird import breakage when combining xarray, dirty_equals and recently released typing-extensions 4.12.1 on Python 3.8.
On second thought it might be better to file this against the typing-extensions project
The text was updated successfully, but these errors were encountered: