You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
darrylthom
changed the title
Message: "falling back to string"
"Could not determine dtype for column X, falling back to string" cluttering console log
Jan 22, 2025
Hi,
I had the same message on one of the computers and no message on the others. After comparing versions, I downgraded fastexcel from 0.12.1 => 0.12.0 and messages disappeared.
Artur
Hello, and thank you for the reproduction case 🙂 There seem to be two different issues here:
There's a log message you'd like not to have. For that, you could either change the logger's level, or completely disable it:
importlogging# This will disable all messages with a level <= WARNINGlogging.getLogger('fastexcel.types.dtype').setLevel(logging.ERROR)
# This will completely disable the loggerlogging.getLogger('fastexcel.types.dtype').disabled=True
2. `fastexcel` tries to determine the dtype for a column that is **not** included in `use_columns`. This indeed seems to be a bug, I'll look into it. Tracked via #327
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: