-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
Inconsistant datatype with type()? #11969
Comments
pls show |
A smaller reproducible example:
|
dupe of #11617 |
@jreback0 |
dupe means duplicate. See the referenced issue which is the same. We get a fair number of duplicates here (no fault of the poster of course). So try to have a single issue. If you look at the referenced issue and it IS not the same, pls let me know. |
@jreback thank you for the info and your efforts. |
@jreback |
@temmplar ok, these ops are not system dependent. but thanks for the info. |
@jreback Furthermore I have some other additional info, which maybe would be a help to backcode the bug, if you need it, please contact me. |
[in]
[out]
Though I can solve it in many cases with
train[cl].dtype
, which gives the correct output:[out]
But if we work with string data types the output will be
object
instead ofstr
as data type.Something shortstop by me or what happens?
Thank you.
The text was updated successfully, but these errors were encountered: