Open ncclementi opened 6 months ago
0 2015-01-01 17:34:56 Name: Cast(date_sec, timestamp), dtype: datetime64[us]
I don't think this is necessarily wrong?
The us
thing is a red herring, that's just how pandas is representing the precision of the timestamp.
epoch seconds should be number of seconds since 1970-01-01 in UTC, so skipping back 5 hours would be correct given your timezone (in January, anyway)
The other precisions are definitely a problem
On main, when casting integers (epoch in seconds for example) to timestamps and executing with polars backends, results are wrong.
Now if we try to cast the milliseconds, microseconds, and nanoseconds passing scale in the timestamp we see way weirder behaviors.
milliseconds
microseconds
nanoconds