Add example of using importlib.resources.files() in Python 3.12

[winstontsai]

This was a helpful example repo. I just have one request.

In Python 3.12 they updated importlib.resources.files(): https://docs.python.org/3/library/importlib.resources.html#importlib.resources.files

Changed in version 3.12: package parameter was renamed to anchor. anchor can now be a non-package module and if omitted will default to the caller’s module. package is still accepted for compatibility but will raise a DeprecationWarning. Consider passing the anchor positionally or using importlib_resources >= 5.10 for a compatible interface on older Pythons.

Could you include an example of omitting anchor so that it defaults to the caller’s module (or explicitly passing the module name with a string literal or __name__? I tried myself and while it works before packaging with zipapp, it fails to open and read the data file when running the zip. I'm not sure if I'm doing something wrong.

[wimglenn]

It looks like this new feature is buggy. I get FileNotFoundError("Can't open orphan path") when trying to use that technique within a zipapp. Are you seeing the same error message?

[winstontsai]

Yes I see that too. I wasn't sure if it was just buggy since it's a relatively new feature or if I didn't understand something.

[winstontsai]

If you also think this is a bug, I will file an issue with cpython.

[wimglenn]

It’s either a bug or a footgun that ought to be documented.

[winstontsai]

Created issue python/cpython#121735

[wimglenn]

In

resources-example/myapp/example5.py

Lines 8 to 10 in 8384ded

	Resist the temptation to use importlib.resources.files() without any arguments, because
	omitting the anchor currently will break zipapp packaging.
	https://github.com/python/cpython/issues/121735

I've added a note advising to avoid this usage until the zipapp issue is fixed.