-
-
Notifications
You must be signed in to change notification settings - Fork 18.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
Type inferencing makes assignment of datetime to an object Series non-idempotent #13910
Comments
I recall an issue exactly like this, but can't seem to find it ( @sinhrks do you remember)? |
pull-requests of course are welcome! |
I suppose so, but what i could find is related to |
I wouldn't be surprised if this is related to numpy/numpy#7619 |
I'm not able to reproduce this.
Is this still an issue?
|
would take a test PR for this |
Code Sample, a copy-pastable example if possible
OK, no worries, we got coerced to integer. Now let's just redo the same assignment:
That's ... suprising. This is probably just an unfortunate feature of a type inference algorithm, but it's awfully shocking.
Related examples for testing
#18410
#21143
Expected Output
The two outputs above would be identical; I'd prefer that they were both the second form (with timestamp information preserved), but anything consistent would be better than the current state.
output of
pd.show_versions()
The text was updated successfully, but these errors were encountered: