-
-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REGR: Index.astype(<numpy string dtype>) started failing #50127
Comments
From git bisect I'm getting #49718 https://www.kaggle.com/code/marcogorelli/pandas-regression-example?scriptVersionId=113299049 |
Weird, sorry for the noise. You are correct |
No worries - @jbrockmendel |
yah i think the np-str-dtype check needs to be added in |
@mroeschke this is a regression, and if we think it's a valid one, not something to bump to 3.0? |
Ah okay fine to still mark at the 2.0 milestone |
take |
For what it's worth, |
EDIT: sorry, this one worked in 1.5 - is it a blocker? |
### What changes are included in this PR? - The issue with numpy 1.25 in the assert equal helper was fixed in pandas 1.5.3 -> removing the skip (in theory can still run into this error when using an older pandas version with the latest numpy, but that's not something you should do) - Casting tz-aware strings to datetime64[ns] was not fixed in pandas (pandas-dev/pandas#50140) -> updating our implementation to work around it - Casting to numpy string dtype (pandas-dev/pandas#50127) is not yet fixed -> updating the skip ### Are there any user-facing changes? No * Closes: #15070 Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
) ### What changes are included in this PR? - The issue with numpy 1.25 in the assert equal helper was fixed in pandas 1.5.3 -> removing the skip (in theory can still run into this error when using an older pandas version with the latest numpy, but that's not something you should do) - Casting tz-aware strings to datetime64[ns] was not fixed in pandas (pandas-dev/pandas#50140) -> updating our implementation to work around it - Casting to numpy string dtype (pandas-dev/pandas#50127) is not yet fixed -> updating the skip ### Are there any user-facing changes? No * Closes: apache#15070 Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
) ### What changes are included in this PR? - The issue with numpy 1.25 in the assert equal helper was fixed in pandas 1.5.3 -> removing the skip (in theory can still run into this error when using an older pandas version with the latest numpy, but that's not something you should do) - Casting tz-aware strings to datetime64[ns] was not fixed in pandas (pandas-dev/pandas#50140) -> updating our implementation to work around it - Casting to numpy string dtype (pandas-dev/pandas#50127) is not yet fixed -> updating the skip ### Are there any user-facing changes? No * Closes: apache#15070 Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
On pandas 1.5:
On the main branch:
This started to fail a while ago on pyarrow's CI (https://issues.apache.org/jira/browse/ARROW-18394). This comes up if you roundtrip a pandas DataFrame with bytes column names to arrow and back to pandas.
Didn't yet investigate further what might be the change that caused this / whether this was intentional, etc.
The text was updated successfully, but these errors were encountered: