-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: Remove fsspec internals from tests #50925
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
CircleCI failure is separate and unrelated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. merging to get ci back to green
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
thx @lithomas1, could you backport manually? |
backported in #51038 |
… tests) (#51038) TST: Remove fsspec internals from tests (#50925) Co-authored-by: Thomas Li <[email protected]>
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.I don't think clearing the registry does anything. The public registry var is supposed to be immutable, and we were just clearing the internal registry dict.
However, we didn't remove gcs from the known_implementations dict, so gcs would've technically still been in the registry IIUC this code correctly.
https://github.com/fsspec/filesystem_spec/blob/0f3ecd8e629043646ab19b1a2b00d895f0553a81/fsspec/registry.py#L206-L209