COMPAT: explictly cast numpy floats to native floats #163
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Numpy 2.0 returns
np.float64
objects instead offloat
, so when rendered with jinja2, values may look like[np.float64(3.2),np.float64(4.383333333333334),np.float64(5.566666666666666)]
instead of[3.2,4.383333333333334,5.566666666666666]
. JavaScript obviously cannot render the former and since there was no error in Python code, the result was just an empty map with errors shows only in the JavaScript console.I hope these are the only cases where this happens but I have no idea how to test that :D. It fixes python-visualization/folium#1905.