order versions appear broken due to recent fsspec changes

@martindurant I see that fsspec.asyn module got rid of maybe_sync function, but older versions of s3fs still rely on the method which now fails to import. For example s3fs==0.5.2 now does not seem to work after a clean install. I see that s3fs requirements.txt asked for fsspec>=0.8.0 and that is now incompatible without an upper boundary.

[martindurant]

Yes, you are right. This is not unusual! If you know you need an older version of s3fs, then you will have to analyse your full set of packages to find compatible versions.

For reference, I mean in the future to do two things:

• move to calendar versioning, since the “semantics” of x.y.z are often confusing for a dev-facing library like this
• always release fsspec, s3fs and gcsfs together
• explicitly pin s3fs and gcsfs’s version to the co-released fsspec. That means more work for me.

[jmcgrath207]

Had a similar issue where fspec 0.9.0 and above don’t work when I use s3fs.S3FileSystem(asynchronous=True however when I downgrade to version 0.8.7 my code is working again. It appears they removed the maybe_sync method.

Traceback (most recent call last):
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/john/PycharmProjects/da_data_pipeline/normalized-redis-lambda/sam/service_logic/__init__.py", line 18, in <module>
    import s3fs
  File "..................../s3fs/__init__.py", line 1, in <module>
    from .core import S3FileSystem, S3File
  File "..................../s3fs/core.py", line 12, in <module>
    from fsspec.asyn import AsyncFileSystem, sync, sync_wrapper, maybe_sync
ImportError: cannot import name 'maybe_sync' from 'fsspec.asyn' (..................../fsspec/asyn.py)

Process finished with exit code 1