I applied somechanges against importlib_resources 6.4 and then merged those with the cpython branch of importlib_resources, then copied the remaining diff over to CPython. These changes represent the re-synchronization of the two codebases, mainly getting the style to align with the linter/formatter's opinion, but also one change to the context managers to be compatible with Python 3.8 syntax.

Since I believe these changes are largely uncontroversial and I was primarily looking to inform Petr of the changes, and because this PR is blocking another, I'm going to merge it, but happy to continue a review or even back out if needed.

Thanks@jaraco for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

GH-123051 is a backport of this pull request to the3.13 branch.

I just noticed that "metadata" appears in the commit message. These changes pertain to "resources".

GH-123051 is a backport of this pull request to the3.13 branch.

Well, to me this looks like style fixes that are traditionally avoided in CPython, but it does look harmless.

GH-123074 is a backport of this pull request to the3.13 branch.

Well, to me this looks like style fixes that are traditionally avoided in CPython, but it does look harmless.

The problem is that it's untenable given the constraints on the CPython repo to have divergent styles between the CPython implementation and the third-party package. Due to its shared maintenance with otherskeleton projects, importlib_resources has a stricter standard for format, types, and lint. There's no VCS metadata to track the differences, so the process of contributing changes fromimportlib_resources (upstream) toimportlib.resources will overwrite any changes that weren't applied upstream. This change does that overwriting so that it's not folded into a subsequent contribution.

Yeah, and from the other side, the custom tooling inimportlib_resources makes it harder than it could be to properly contribute toimportlib.resources.
I wonder if we should we addimportlib.resources toPEP-360, or otherwise makeimportlib_resources's style requirements, or contribution instructions in general, more discoverable?

I wonder if we should we addimportlib.resources toPEP-360, or otherwise makeimportlib_resources's style requirements, or contribution instructions in general, more discoverable?

I don't think adding it to PEP 360 would help much, given that the external project already provides most of that context (who maintains it, which versions are compatible), and the two codebases are maintained jointly. I note also thatimportlib_metadata andzipp follow the same regime, and at least for those, the CPython docs to provide a link to the external mirror / backport. I note also that I run into similar issues withconfigparser, even though it follows amore conventional backport role,backports.tarfile,singledispatch, and probably others.

On several occasions, I've wanted to have a good place to document this regime, to include contribution instructions and maintenance instructions, but the main thing that's held me back is lack of an appropriate shared space (it felt awkward to put the docs in one project that apply equally to three). I seem to recall at one point I did document the process, but I'm unable to find it. Correction, Ifound it here. That guidance is still somewhat relevant, but also out of date and incomplete. I should probably just revive that doc in a maintained repo/wiki (probably importlib_metadata), and just link to it from the relevant projects. We should also update theimportlib.resources docs to provide a reference toimportlib_resources.

My preference is to accept changes in the external project first for several reasons, that I'll document in the contributing guide, but I'm happy to accept contributions in CPython as long as the contribution is amenable to a backport.