-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
datetime64 can no longer be serialized with numpy 2.1??? #9423
Comments
maybe related to #9399 |
Indeed, the changes in #9403 appear to fix this. However, I can only reproduce with ds["timestamp"] = np.datetime64(datetime.now(UTC)) If instead I use ds["timestamp"] = np.datetime64(datetime.now(UTC), "ns") it doesn't fail. So this also depends on the units of the |
I've seen the
maybe i'm just crazy though:
and 292 years is fine if you consider the date starts from 1974. <-- is this true? |
I think the timestamps should start from There have been requests to relax the restriction to |
Right so the question is, do we care about the year 2262?
so i think i'm over thinking it for 2024 in my own code base, so I can start to sprinkle |
I believe this has been fixed by #9403 |
Thanks! Excited to remove my hacks in the next release! |
Please have a look here for a possible first step on that road: #9580 |
What happened?
It seems that numpy 2.1 broke some type checking with datetime64 and now it makes it difficult to serialize them?
Oddly enough, you cannot recreate this with numpy 2.0. Only 2.1
What did you expect to happen?
for it to work ;)
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
No response
Anything else we need to know?
Environment
The text was updated successfully, but these errors were encountered: