Development tool stack

[ap--]

Hello everyone,

Is the development and packaging tool stack that should be used for fsspec projects already known?
I am asking, because a request to modernize the devtools was brought up by @brl0 in fsspec/universal_pathlib#98, and I think it might make more sense to concentrate the effort on helping to create the cookiecutter template.
Since everyone has (imo way too strong 😅 ) opinions about these things, I would prefer to just follow the template so that it's easy to switch context between the different projects.

Since universal_pathlib doesn't derive its own FileSystem class, it's probably not the ideal target use case. But I could imagine that workflow templates, package versioning and linting etc would be common ground.

Let me know what you think,
Cheers,
Andreas 😄

[efiop]

See fsspec/community#6

[efiop]

We've used https://github.com/iterative/py-template or bits and pieces of it in sshfs, ossfs, adlfs, etc Take a look, maybe you'll like it too (i'm biased since this is our company's template). It is not ideal and we haven't added ruff to it yet, but it is the closest thing that we currently have for our purposes in iterative team. Maybe it could serve as inspiration