-
Notifications
You must be signed in to change notification settings - Fork 36
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
File not found in write_
and read_
functions when filepath contains tilde
#1085
Comments
Just to note: Using a tilde worked previously; I noticed this error only recently. |
write_
and read_
functions when filepath contains tilde
Thanks for the report, do you want to make a PR for this? I think this should be solved using |
@etiennebacher Will do. However, before doing so, do you think the cause is on the rust side? Perhaps with the update to 0.39.0? I cannot work out why tilde is only now causing problems. I agree this can be solved using Lines 1949 to 1973 in 6fdd4a9
If we end up using |
My bad, I thought this error was for I can't see any recent changes in the R or Rust methods that would explain this failure so it's probably from rust-polars: https://github.com/pola-rs/r-polars/blame/1de4d0dfdf83228f2d4933fc7d8239a565d907fa/R/dataframe__frame.R#L1949 Do you remember what was the last package version for which it worked? |
They already normalize the file path in python but I can't find a recent commit that changed that, so I suppose passing a path starting with |
Might be worth checking node.js and polars-cli |
I believe it worked before the update to rust-polars 0.39.
I suppose we should implement the equivalent normalization if |
I don't know if this is the change was intended upstream or not. I think it could be a bug. |
I think so, especially since they handle the
It could be but the file where |
There seems to be an issue locating files when the filepath/source contains a tilde (e.g.
"~/Desktop/some_file.csv"
). This is a common pattern for macOS users. Any ideas what might be causing this?Created on 2024-05-07 with reprex v2.1.0
I checked the Python implementation and it works as expected:
Created at 2024-05-07 15:27:21 BST by reprexlite v0.5.0
The text was updated successfully, but these errors were encountered: