You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It certainly looks like it ought to work, but can I ask why you are calling it in that manner? For your information, fastparquet does try to guess whether the function passed is actually an fsspec filesystem implementation method, so that must be the difference - you can equally pass fs= in that case.
I am working with both pathlib and S3 paths in our pipeline and I want to avoid checking before each call which of the two I have. So I implemented an S3Path analog to pathlib.Path which has a function similar to the one below:
I would say this is a genuine bug, and the code deciding what to do with file-like objects versus fsspec-specific files should be revisited. Are you able to do any debugging?
I am running into a very weird issue when using a modified version of
S3FileSystem().open
withfastparquet.Parquet
file:The issue resolves when I use
open_with=s3.open
instead.The trace is below:
The text was updated successfully, but these errors were encountered: