-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Bug in .to_datetime() when passing integers or floats, no unit and errors=coerce #13183
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
Conversation
f0a15c8
to
5fee2db
Compare
note that prior to 0.18.1 we would handle
|
any comments @jorisvandenbossche |
…nd errors=coerce closes pandas-dev#13180
@melzoghbi if you still have an issue, please open a new issue (as your example is not related to the above issue). However, please first make sure to test on the latest pandas (0.21.0) and make sure to have an actual reproducible examples (so copy-pasteable code, not as an image). Further, for me this actually converts to a datetime:
|
Thanks for your help and this actually shows the datetime but not the actual date that i am looking for. For example: Should show a date as 11/14/27 but it actually shows epoch time as of 1970 datetime. Any way i will open a new issue for this. |
issue persists in pd 0.23.3 |
this is still an issue in the Pandas |
This is a closed issue that is fixed. If you think there is still a bug, please open a new issue with a reproducible example. If it is about the year 1970, that is not a bug but because
|
closes #13180