feat: Support Python 3.12

[edgarrmondragon]

What do these changes do?

Communicates official support for Python 3.12

Are there changes in behavior for the user?

No

Related issue number

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> (e.g. 588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the PR
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

[amotl]

Dear @asvetlov and @webknjaz,

thanks a stack for conceiving and maintaining the excellent yarl package. We have been tripped by missing support for Python 3.12 at daq-tools/influxio#57.

May we humbly ask if you have the capacity to bring in this patch, or, alternatively, if you would accept any kind of support on this matter?

Keep up the spirit, and with kind regards,
Andreas.

[edgarrmondragon]

The linter checks seem to be failing upstream in master too 😕

[webknjaz]

Yep, I'll fix that. Could you use the rebase button next time?

[webknjaz]

@amotl this PR only modifies some metadata. The runtime support is already present on master.

[webknjaz]

Additionally, I'd add a separate change note 942.contrib.rst to notify the contributors about requiring Python 3.12 CI jobs to pass in pull requests.

[webknjaz]

We write (most of the) individual change note fragments in the past tense, because they're targeted at the end-users and don't necessarily contain information about internal implementation details or decision.
Changelog is supposed to describe what changed compared to the previous version.

Individual fragments should have the same style. When looking at individual PRs on GitHub, it's unobvious and is hard to judge whether it “fits”.

However, we have RTD PR builds enabled, so it's possible to preview at https://yarl--942.org.readthedocs.build/en/942/changes.html whether a fragment contributes to the changelog being cohesive.

I think, this phrase can be rephrased to describe more accurately what the PR does, with the end-users being the target audience in mind.

Suggested change

	Official support for Python 3.12.
	Declared Python 3.12 supported officially in the distribution package metadata
	-- by :user:`edgarrmondragon`.

[webknjaz]

With the below note in mind, I'd change this fragment type from misc to packaging. I recently added more clear categories for the Towncrier fragments that should reflect the changelog sections better.

[edgarrmondragon]

Thanks, done in 810c06e

[edgarrmondragon]

Ah, PSF Chronographer / Timeline protection is complaining now:

No files matching re.compile('news/(?P<issue_number>[^\\./]+)\.(?P<fragment_type>feature|bugfix|doc|removal|misc)(\.\d+)?(\.[^\\./]+)*$') pattern added

https://github.com/aio-libs/yarl/pull/942/checks?check_run_id=18803866754

[webknjaz]

Ouch.. Looks like I need to teach the bot about an extra config file. Totally not your fault. I'll force-merge if need be.

[edgarrmondragon]

Aha I do see https://github.com/sanitizers/chronographer-github-app/blob/8b65b3de7ebb55a76d3f930f29d0ec9681da711d/chronographer/file_utils.py#L14-L39.

Let me know if I can help in any way 🙂.

[webknjaz]

Exactly. When I first wrote that code, I didn't know that an alternative config path fallback exists. Though, it's no big deal. I'll correct it and redeploy later.

[webknjaz]

So it looks like that contrib file is still needed..

[amotl]

Hi again,

thank you so much for concluding this patch and running a release. This downstream patch demonstrates it works well.

• Add support for Python 3.12 daq-tools/influxio#57

Keep up the spirit, and with kind regards,
Andreas.