BUG: coerce empty-string IEEE NaN to null for pyarrow floats - #421
BUG: coerce empty-string IEEE NaN to null for pyarrow floats#421xirafa wants to merge 4 commits into
Conversation
|
Warning Review limit reached
Next review available in: 15 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
d1e83ea to
7cda74c
Compare
Empty CSV fields with keep_default_na=False stored IEEE NaN in double[pyarrow] instead of raising like numpy float64.
Move the GH#66834 whatsnew note to I/O to resolve the Missing-section conflict. Empty-string conversion now skips pd.NA and raises using pa_type.
Mirror of pandas-dev/pandas#66837. Runs the pandas test suite through dagz.