diff_report = profile1.diff(profile2) -> Object of type int64 is not JSON serializable
See original GitHub issueGeneral Information:
- OS: OSX
- Python version: python 3.8
- Library version: current
Describe the bug:
Object of type int64 is not JSON serializable
Problem:
'conservative': {'df': xxxx, 'p-value': 0.0}, 'welch': {'df': xxxx, 'p-value': 0.0}}
To Reproduce:
diff_report = profile1.diff(profile2)
json.dumps(diff_report)
Expected behavior:
Screenshots:
Additional context:
Issue Analytics
- State:
- Created 2 years ago
- Comments:29 (20 by maintainers)
Top Results From Across the Web
Python - TypeError: Object of type 'int64' is not JSON serializable
I have a data frame that stores store name and daily sales count. I am trying to insert this to Salesforce using the...
Read more >[Fixed] Object of Type int64 Is Not JSON Serializable
Sometimes, while creating a JSON object, your program might run into the TypeError exception with the message “object of type int64 is not...
Read more >TypeError: Object of type \'int64\' is not JSON serializable ...
I am trying to insert this to Salesforce using the below Python script. I, however, get an error. TypeError: Object of type 'int64'...
Read more >TypeError: Object of type 'int64' is not JSON serializable (error ...
It works fine for the first couple of epochs, but suddenly throws this error afterwards. I tried my code using a different bayesian...
Read more >TypeError: Object of type int64 is not JSON serializable
DataFrame.min() is returning a 0 as an int64, which does not bother my laptop on Ubuntu 21.04, PyStan3.2, etc.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Excellent - thanks, both!
Fix incoming soon: @turtlemonvh, ty for identifying the issue!