Closed jorisvandenbossche closed 1 week ago
Owee, I'm MrMeeseeks, Look at me.
There seem to be a conflict, please backport manually. Here are approximate instructions:
git checkout 2.3.x
git pull
Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 ee3c18f51b393893ed6e31214c7be2f9427ce0c9
You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #60321: TST (string dtype): resolve all xfails in IO parser tests'
git push YOURFORK 2.3.x:auto-backport-of-pr-60321-on-2.3.x
"Backport PR #60321 on branch 2.3.x (TST (string dtype): resolve all xfails in IO parser tests)"
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 Still Needs Manual Backport
label once the PR gets merged.
If these instructions are inaccurate, feel free to suggest an improvement.
Will backport this one too
Manual backport -> https://github.com/pandas-dev/pandas/pull/60330
There are two remaining xfails left: one related to invalid unicode (that errors if using the pyarrow-backed string dtype, so we should probably have a fall back to object dtype fo that case), and another one about specifying the
names
keyword with the pyarrow engine giving object-dtype columns.xref https://github.com/pandas-dev/pandas/issues/54792