Andreas Poehlmann

Hi @BartSchuurmans Regarding the implementation, imo behavior here is correct. This only works for your `pathlib.Path` attributes because of lax mode: https://docs.pydantic.dev/latest/concepts/conversion_table/#__tabbed_1_1 See: ```pycon >>> from pathlib import Path ......

Hi @pmeier and @andrewfulton9 > Would you be open to integrate this into the UPath class optionally when pydantic is available in the environment? Very much so. Yes. Regarding serialization:...

Hello @scholtalbers Here is an explanation for how all of this works together. Some of it skips over details, so I really recommend to read the filesystem_spec docs thoroughly and...

I noticed the same issue in universal-pathlib where the gcs tests where very slow, and it only occurred without a working internet connection, because then all the timeouts accumulated. setting...

Ping me once you fix the `Optional[str]` issue on your side. I can then release a new intermediate version of `universal-pathlib` with the #257 fix.

Hi @chengdonglin Could you provide a minimal example to reproduce your issue?

Can you provide more context? The following style for creating paths is implemented for s3, gcs and az object storage: ```python >>> import upath >>> upath.UPath("A/B/C/filename.tar.gz", protocol="gs", bucket="bucket-name") GCSPath('gs://bucket-name/A/B/C/filename.tar.gz') ```

So from my understanding, to stay in the google storage vocabulary, you'd want the `OBJECT_NAME`, whereas right now you can only retrieve the `PATH_TO_RESOURCE` = `BUCKET_NAME/OBJECT_NAME`. This will become generally...

In a future version `.key` could be made available with the implementation below: ```python >>> import upath >>> x = upath.UPath("gs://bucket/abc/efg/file.txt") >>> x.path.removeprefix(x.anchor) 'abc/efg/file.txt' ``` More general, relative path behavior...

Hi @danielgafni Thank you for reporting! Could you check 3 things: - did this change with recent fsspec versions? (Just try installing the newest vs installing one from