Skip to content
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

(fix): extension array indexers #9671

Open
wants to merge 187 commits into
base: main
Choose a base branch
from

Conversation

ilan-gold
Copy link
Contributor

Identical to kmuehlbauer#1 - probably not very helpful in terms of changes since https://github.com/kmuehlbauer/xarray/tree/any-time-resolution-2 contains most of it....

kmuehlbauer and others added 30 commits October 18, 2024 07:31
…ore/variable.py to use any-precision datetime/timedelta with autmatic inferring of resolution
…t resolution, fix code and tests to allow this
… more carefully, for now using pd.Series to covert `OMm` type datetimes/timedeltas (will result in ns precision)
…rray` series creating an extension array when `.array` is accessed
kmuehlbauer and others added 26 commits January 9, 2025 09:29
…ll back to cftime encoding, add fix for cftime issue where python datetimes are not encoded correctly with date2num.
* Fix timedelta encoding overflow issue; always decode to ns resolution

* Implement time_unit for decode_cf_timedelta

* Reduce diff
@kmuehlbauer
Copy link
Contributor

@ilan-gold Can you rebase your changes on latest main? PR #9618 just got merged.

@ilan-gold
Copy link
Contributor Author

@ilan-gold Can you rebase your changes on latest main? PR #9618 just got merged.

I think I did. The tests look good but I'll have to re-check tomorrow - it was just mypy failing before but now I picked up an actual test failure

@kmuehlbauer
Copy link
Contributor

Yes, looks clean. I was irritated by the amount of commits. But this will be squashed anyway, or do I miss something.

The error

ERROR xarray/tests/test_distributed.py::test_dask_distributed_zarr_integration_test[True-True] - Failed: 9 thread(s) were leaked from test

seems unrelated. But it's also on main now. Not sure how to debug this...

@ilan-gold
Copy link
Contributor Author

Great @kmuehlbauer - I want the maintainers to look at the MyPy. I could in theory fix it, but I would basically be guessing at what their wishes are for the classes' return types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants