-
Notifications
You must be signed in to change notification settings - Fork 6
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
Management of pandas object #140
Comments
Can you a be a bit more precise ? |
For the moment, I am not that the support of pandas array is everywhere. The minimal support is to support pandas has input array and transform everything into numpy arrays. |
Thx for clarifying. When you say input/output, you think of CPI ? Until recently, I would have said: we consider only numpy arrays (and thus convert dataframes in a first step), but I increasinlgy think that X can be provided as a DataFrame, because it handles heterogeneous data, e.g. strings, floats etc. |
I was thinking in general.
Yes, this is one proposition. However, I am not an expert on pandas and I don't know yet the subtlety between the different types of pandas. From a quick look at pandas, I see that the main type is DataFrame. In this case, if we want to support pandas, we should handle DataFrame.
A short comment, numpy can also handle heterogeneous data even if it's not really targeting it. |
For the moment, the management of pandas is not handled by all the methods. In the refactoring, I remove the management of and replace with only a transformation of data to numpy arrays.
In the long term, we need to provide a homogeneous way to handle the pandas's objects.
The text was updated successfully, but these errors were encountered: