-
-
Notifications
You must be signed in to change notification settings - Fork 19.4k
BUG: Recognize chained fsspec URLs #61041
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
Conversation
|
Just confirming that there isn't a solution alluded to in #48978 (comment) where |
I checked the latest fsspec API reference and couldn't find any public functions for validating URLs. |
|
Thanks @snitish |
|
Thanks @snitish! I thought the bug was going to get closed the same week as when I documented the root cause and the bullet point solution. Took a few years in the end! |
|
Wow, I filed this bug in October 2022. I am super pleased to have it fixed. It would be churlish to complain about the amount of time it's taken--instead, I am just impressed by how inexorable progress seems to be! |
|
Could this fix also be applied to 2.3.x ? |
doc/source/whatsnew/v3.0.0.rstfile if fixing a bug or adding a new feature.The new
(::[A-Za-z0-9+\-+.]+)*part of the regex will allow for optional::<alphanumeric+-.>-like strings before the://section of the URL, which will enable it to recognize chained fsspec URLs.