-
Notifications
You must be signed in to change notification settings - Fork 145
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
Pandas data type 'string' not understood #93
Comments
Looks like the required numpy version ( I reproduced it as follows:
These libraries all seem to be compatible with one another (otherwise pip would show a warning or automatically update libraries to compatible versions, neither of which happened). I fixed it by updating numpy:
I can also fix the issue by just explicitly converting each column to
I'm running Ubuntu 22, in case it matters. |
Commenting to keep the issue alive, since I just faced the same problem while running the Univariate Drift Detection tutorial. Manually updating numpy worked for me as well. |
Thanks for the extra information all. We'll try to include a fix in the next release, coming next week! |
Sorry for missing this Bernhard, I was out on holiday. Thanks for the report and the investigation! |
Nice dig down! On the latest version, 0.5.3, with this code sample:
the issue is not reproducable on my end with numpy 1.22.4 and pandas 1.4.3 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the bug
Running the Quickstart results in an error
To Reproduce
Steps to reproduce the behavior:
Runing:
Gives the following error:
Expected behavior
The quickstart code runs without a problem.
Additional context
The user who had that issue was running python 3.8 on windows through a pycharm environment.
I couldn't reproduce the error when I tried on my machine. Moreover when I guided the user to set up a new conda environment the error went away.
However maybe the way string type is defined here could be changed similar to suggestions such as these to cover more cases? I 'd hold of on that until we see more users having the issue, since in this case a misconfigured environment is more likely the problem than a library compatibility issue.
The text was updated successfully, but these errors were encountered: