-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Confusing warning when calling read_csv() with fsspec URL #19150
Comments
Anyone know the status of this? I haven't contributed to polars before but would love to pick it up, but looks like @ComputingVictor had a PR in place but closed it before it could merge? |
I haven't tried to reproduce this since, but #19154 may have fixed this |
Feel free to contribute. I closed due to incompatibilities with the new version of Polars! |
Indeed, gh-19154 fixed this, the warning no longer appears in Polars 1.10 ✔️ (Gracias @ComputingVictor for giving it a try!) |
Thanks for checking @astrojuanlu, I'll close this then! |
Checks
Reproducible example
Log output
Issue description
The text of the warning is confusing. What Polars received (a filename) and what would be optimal (a path to the file) sound identical to me; one of those is probably wrong.
Expected behavior
Aside from the text of the warning, I also did not expect to receive this warning when using fsspec URLs. I believe in an earlier version you got this warning when you passed an open file to a read function, but passing an open file no longer triggers this warning.
Installed versions
The text was updated successfully, but these errors were encountered: