BUG: read_csv with dtype=bool[pyarrow] #53391
Conversation
doc/source/whatsnew/v2.0.2.rst
Outdated
| @@ -31,6 +31,7 @@ Bug fixes | |||
| - Bug in :func:`api.interchange.from_dataframe` was unnecessarily raising on bitmasks (:issue:`49888`) | |||
| - Bug in :func:`merge` when merging on datetime columns on different resolutions (:issue:`53200`) | |||
| - Bug in :func:`read_csv` raising ``OverflowError`` for ``engine="pyarrow"`` and ``parse_dates`` set (:issue:`53295`) | |||
| - Bug in :func:`read_csv` when defining ``dtype`` with ``bool[pyarrow]`` (:issue:`53390`) | |||
There was a problem hiding this comment.
This is only for "c"/"python" parsers, right?
Might want to clarify that here.
There was a problem hiding this comment.
Yeah correct, updated.
| False | ||
| True | ||
| """ | ||
| result = parser.read_csv(StringIO(data), dtype={"col": "bool[pyarrow]"}) |
There was a problem hiding this comment.
Can you add a test for dtype_backend=pyarrow as well?
There was a problem hiding this comment.
Sure, I modified test_EA_types to test this instead
|
Ah sorry, I forgot the 2.0.2 release was today. Can you move the whatsnew note to 2.0.3? |
|
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
* Backport PR #53391: BUG: read_csv with dtype=bool[pyarrow] * Add xfail
* BUG: read_csv with dtype=bool[pyarrow] * Use existing test instead * Clarify whatsnew * Move to 2.0.3
* BUG: read_csv with dtype=bool[pyarrow] * Use existing test instead * Clarify whatsnew * Move to 2.0.3
dtypeis defined withbool[pyarrow]#53390 (Replace xxxx with the GitHub issue number)doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.