Change .str.to_datetime
to default to microsecond precision for format specifiers "%f"
and "%.f"
#13592
Closed
2 tasks done
Labels
A-temporal
Area: date/time functionality
bug
Something isn't working
P-medium
Priority: medium
python
Related to Python Polars
Milestone
Checks
Reproducible example
Log output
Issue description
This also seems to happen for all dates above "2262-09-18 00:00:00.0" and below "1677-09-18 00:00:00.0".
Note: I only tested the upper and lower boundary of the years until the exception was thrown. Month and day may vary.
Expected behavior
The expected behavior, to my mind, would be a conversion to Datetime. Especially in the cases of "1677-09-18 00:00:00.0" or "2262-09-18 00:00:00.0".
For the case of "0920-09-18 00:00:00.0" the original date that threw this exception, if indeed it should fail at least the error should be more descriptive than the existing one. For example, using the same exception that is thrown when the wrong format is applied
pl.ComputeError
Installed versions
The text was updated successfully, but these errors were encountered: