Non-"binary" resources are already in widespread use, so perhaps that requirement shouldn't be in the docs at all. In practice, a resource is "any data file other than a Python source file."
Moreover, I see no reason why a resource name in general shouldn't be allowed to contain a "/" character! Perhaps the simplest way to implement such a thing is to leave all the existing importlib.resources APIs unchanged, but then add a separate function that grants access to collections of resources within a package. Maybe this is as simple as adding a `dir=` kwarg to importlib.resources.files(), defaulting to `dir=None`. _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/M34PRCIZGY4ZJIC6KLYNFS6HGJGNXEEX/ Code of Conduct: http://python.org/psf/codeofconduct/
