API: Clarify the type of AbstractFileSystem.protocol

It seems like AbstractFileSystem.protocol can be either a str or a Tuple[str], for subclasses that use multiple proctocols like gcs or gs.

I think it’d be cleaner to have protocol always be a str, and add a property protocols for cases where we need to refer to them all.

def protocols(self) -> Tuple[str]:
    """A tuple of protocols for this FileSystem. Just `self.protocol` by default."""
    return (self.protocol,)

[jrbourbeau]

This is on my todo list for this week, thanks for outlining these steps @TomAugspurger!

Using __subclass_init__ would restrict fsspec to Python 3.6+ (which is fine by me as it seems several other packages in the community, e.g. pandas, dask, distributed, any packages that are following NEP 29, have all dropped support for 3.5). @martindurant @TomAugspurger do you have thoughts on dropping Python 3.5 here?

[TomAugspurger]

Dropping 3.5 is fine by me.

On Wed, Nov 13, 2019 at 11:38 AM James Bourbeau [e-mail] wrote:

This is on my todo list for this week, thanks for outlining these steps @TomAugspurger https://github.com/TomAugspurger!

Using subclass_init would restrict fsspec to Python 3.6+ (which is fine by me as it seems several other packages in the community, e.g. pandas, dask, distributed, any packages that are following NEP 29 https://numpy.org/neps/nep-0029-deprecation_policy.html, have all dropped support for 3.5). @martindurant https://github.com/martindurant @TomAugspurger https://github.com/TomAugspurger do you have thoughts on dropping Python 3.5 here?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/intake/filesystem_spec/issues/179?email_source=notifications&email_token=AAKAOIXEH4PCUYINFTE7BWLQTQ3SFA5CNFSM4JKSDU3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED7ALMY#issuecomment-553518515, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKAOISD5MITLPRQBHF7MULQTQ3SFANCNFSM4JKSDU3A .