Support for data URI scheme? about universal_pathlib HOT 5 CLOSED

What would be the use case for this? Why not just use a bytes buffer?

from universal_pathlib.

My use case is for loading resources from web pages, such as images or CSS style-sheets. A resource link is typically a web address or a data URI:

<img src="http://example.com/image.png">
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg==">

A DataPath class would allow universal_pathlib to be used to load both of these resources without having to handle data URIs separately - making it even more universal.

I currently have a DataPath implementation, which I register in upath.core.registry to make this work.

I was wondering if you'd consider including non-fsspec backed Path classes as part of this library?

from universal_pathlib.

I currently don't see how this is a good use case. If I understand correctly, the only useful method would be .read_bytes(), and none of the others would make sense in this example.

Is there another example with data uris that requires more functionality for path handling?

from universal_pathlib.

I agree with @ap--. If you have a DataPath implementation and can register that with upath in your application, that is great! I don't think it is a great fit for this library because there is limited added-value in terms of path handling.

from universal_pathlib.

Fair enough

from universal_pathlib.