We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On released version, we see this behaviour:
In [1]: idx = pd.Index(['あ', b'a'], dtype='object') In [2]: idx Out[2]: Index(['あ', b'a'], dtype='object') In [4]: idx.astype(str) Out[4]: Index(['あ', 'a'], dtype='object')
So where the bytes object b"a" gets converted to the string "a".
bytes
b"a"
"a"
On master (since a few days), however, we now get:
In [7]: idx.astype(str) Out[7]: Index(['あ', 'b'a''], dtype='object')
so where the bytes object gets converted to the string "b'a'"
"b'a'"
Possibly due to #38518 cc @jbrockmendel
The text was updated successfully, but these errors were encountered:
add code sample for pandas-dev#38607
0d719ae
can confirm, first bad commit: [7043f8f] REF: use astype_nansafe in Index.astype (#38518)
Sorry, something went wrong.
hit the revert button b4 becomes more difficult to revert.. #38610
reverting makes sense short term.
longer-term, does this affect other places where astype_nansafe is called?
Successfully merging a pull request may close this issue.
On released version, we see this behaviour:
So where the
bytes
objectb"a"
gets converted to the string"a"
.On master (since a few days), however, we now get:
so where the
bytes
object gets converted to the string"b'a'"
Possibly due to #38518 cc @jbrockmendel
The text was updated successfully, but these errors were encountered: