Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@audeoudh

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

The CLA has been signed (according to the knight).

It was a long time I did not check this PR. I hope I did not forget something in the meantime.

I rebased the work on current main branch. I took @serhiy-storchaka's review into account.

I suppose I should squash before the merge, shouldn't I? Just let me know, I'll do it.

I rebased the work on current main branch.

Force-pushing does not play well with GitHub and reviews. I would suggest to use git merge --no-ff main instead of git rebase main, as the review history is kept intact.

I suppose I should squash before the merge, shouldn't I? Just let me know, I'll do it.

No need; all PR's are squashed upon merging :)

Force-pushing does not play well with GitHub and reviews. I would suggest to use git merge --no-ff main instead of git rebase main, as the review history is kept intact.

True for GitHub reviews. But merge --no-ff without rebase does not play well with git log itself.

But if all PR's are squased upon merging, it does not need to be rebased. Thanks for the tip.