BUG: fix .str.isdigit to honor unicode superscript for older pyarrow

[jorisvandenbossche]

• closes BUG: Series.str.isdigit with pyarrow dtype doesn't honor unicode superscripts #61466
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

[jbrockmendel]

pandas/tests/strings/test_strings.py::test_isnumeric_unicode

[jorisvandenbossche]

pandas/tests/strings/test_strings.py::test_isnumeric_unicode

Yeah, see #61466 (comment) (but I suppose the best option is just to accept that difference and update the test to reflect it. Alternatively we could still only use pyarrow for ascii, and always fall back to python for unicode, if we really want consistent behaviour)

[jorisvandenbossche]

cc @mroeschke this should also fix the doctest failure on main

[mroeschke]

Error:...:GL07:pandas.Series.str.isdigit:Sections are in the wrong order. Correct order is: Returns, See Also, Notes, Examples

[mroeschke]

Thanks @jorisvandenbossche (the other failures appear to be due to a numexpr upgrade)

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 2.3.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 f14f131805aa07f3f2e2a4b8185520e916f01be4

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #61962: BUG: fix .str.isdigit to honor unicode superscript for older pyarrow'

4. Push to a named branch:

git push YOURFORK 2.3.x:auto-backport-of-pr-61962-on-2.3.x

5. Create a PR against branch 2.3.x, I would have named this PR:

"Backport PR #61962 on branch 2.3.x (BUG: fix .str.isdigit to honor unicode superscript for older pyarrow)"

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.

[jorisvandenbossche]

Manual backport -> #62476