-
Notifications
You must be signed in to change notification settings - Fork 903
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
Use fsspec's infer_storage_options #1714
Conversation
Signed-off-by: Antony Milne <[email protected]>
Looks like fsspec has done a release a couple of days ago 😄 |
@MerelTheisenQB indeed, but unfortunately it got reverted a couple of days later since apparently it broke other stuff 😬 I'm trying to figure out whether there's a solution on their side: fsspec/filesystem_spec#1002. If not then I'm afraid we'll have to keep our own |
Ah that's a pity.. 😞 |
Unfortunately I don't think this is going to be fixed on the fsspec side soon, so we will continue to maintain our own The immediate call for this was to add the gdrive protocol, which I'm doing here: #1708 |
The original issue of replacing Quote
I feel like if we just move this line it should work? if protocol in CLOUD_PROTOCOLS: |
Description
Closes: #1632.
Thanks to fsspec/filesystem_spec#988 we no longer need to write our own version of fsspec's
infer_storage_options
. However, we do need to wait until they do a release before we can use that code.The tests in this PR will only pass once fsspec do that release and we edit our requirements.txt to include that new version of fsspec. So we need to keep an eye on fsspec to see when that release happens. When it does:
TODO
to get the new fsspec version in as a dependencytest_parse_filepath
completely (it's no longer needed since it will all be tested on the fsspec side)Note that removing
CLOUD_PROTOCOLS
was only ever used in_parse_filepath
and never advertised anywhere, so even though it's not got_
in front of it I think it's fine to remove. If anyone wanted to use it to modify the list then they would have raised an issue to modify it on the kedro side (which has happened in the past). So I think we can safely remove this variable.Checklist
RELEASE.md
file