-
-
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
Float conversion makes fillna lossy #24537
Comments
actually no, you are right this is lossy. |
(Internet is down, typing with thumbs for a while) I’ve poked at this a bit for interpolate; if the int64 vals fall inside int32 bounds then we are OK. Otherwise need to cast to float128 to be assured lossless. |
This looks okay on master now. Could use a test
|
Hi @mroeschke, I would like to contribute. Can you provide a little guideline on what to test on? Thanks |
@KianYang-Lee would need a test to validate that the code snippet in the original post returns the result in my previous comment. |
OK taking this. will come up with the test and result soon |
@KianYang-Lee are you still working on this? |
@jackgoldsmith4 |
No, I'm not. Got caught up with work. Sorry and Please proceed
|
For int64 data near the int64 implementation bounds,
astype('float64')
orensure_float64
is lossy. The motivating case isPeriodArray.fillna
The text was updated successfully, but these errors were encountered: