Skip to content

BUG: read_json not reading in large ints properly #41107

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

Closed
wants to merge 2 commits into from

Conversation

lithomas1
Copy link
Member

@lithomas1 lithomas1 commented Apr 22, 2021

@lithomas1 lithomas1 added Bug IO JSON read_json, to_json, json_normalize labels Apr 22, 2021
@lithomas1 lithomas1 requested review from jreback and WillAyd April 23, 2021 01:23
@lithomas1 lithomas1 added the Numeric Operations Arithmetic, Comparison, and Logical operations label Apr 23, 2021
@WillAyd
Copy link
Member

WillAyd commented Apr 26, 2021

Casting to int64 / float64 is unfortunately not going to work generically here. I think @arw2019 was closer to a solution in #34984 - maybe something you can pick up?

@lithomas1
Copy link
Member Author

OK, closing then. Python C API stuff is a little bit over my head.

@lithomas1 lithomas1 closed this Apr 27, 2021
@lithomas1 lithomas1 deleted the json-large-int branch May 4, 2021 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug IO JSON read_json, to_json, json_normalize Numeric Operations Arithmetic, Comparison, and Logical operations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

read_json reads large integers as strings incorrectly if dtype not explicitly mentioned
2 participants