Lazy registry #78
Merged
Lazy registry #78
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello everyone,
This PR allows to import
upath.registrywithout import overhead of implementations and their dependencies. It provides a functionupath.registry.get_upath_classthat takes a protocol, and returns either a specialized implementation of UPath, or the default UPath class if no specialization is available. It returns None if no corresponding fsspec filesystem can be found.Furthermore, the untested warning for
file:/protocol UPath instances is removed, since we explicitly test the UPath class with all test cases for thefileprotocol intest_core.py.Cheers,
Andreas 😃