Open Nitro963 opened 2 months ago
Thanks for the report! pandas compares the supplied path to the spec as specified in RFC 3986 and concludes it is not a URI. Namely, the use of ::
in the scheme section. See https://datatracker.ietf.org/doc/html/rfc3986#section-3.1 for details.
Possible options are to leave the logic as-is or to just assume a URI when a user passes storage_options
. It's not clear to me what the best path forward is, further thoughts and investigations are welcome!
Pandas version checks
[ ] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pandas.
[ ] I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
The provided code snippet will fail and raise a ValueError. Although that the provided URL is indeed a valid fsspec file path.
Expected Behavior
pd.read_*
should integrate out of the box with the providedstorage_option
as it contain valid keyword arguments forfsspec.open
Installed Versions