-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
"Could not determine dtype for column X, falling back to string" cluttering console log #326
Comments
Hi, |
Hello, and thank you for the reproduction case 🙂 There seem to be two different issues here:
|
@lukapeschke I'd have to introduce statements |
Hello @darrylthom A fix for this issue was just merged 🙂 You should only get the warning for columns included in |
@bzm3r Python's logging module can also be configured through shared config files: https://docs.python.org/3/library/logging.config.html#logging.config.fileConfig . But with the recently merged fix, you should get less warnings if you're using If you want to try the latest fastexcel version out, wheels are available here:
|
I am using Polars to do read_excel which is interfacing with the fastexcel wrapper. In cases where I have a column in my Excel sheet with only nulls, it is giving me this message with no way to stop it. It did not seem to give these messages in the past.
A use case would be a Comments column in a master data worksheet that I might have not had to utilize yet. This would be totally expected, but now I get warnings about falling back to string that clutters the console log and may lead a dev to thinking the code is producing errors.
Additional context: pola-rs/polars#20832 (comment)
polars-errors.zip
The text was updated successfully, but these errors were encountered: