Test Python 3.13

[kurtmckee]

Python 3.13 will be released in a few days (its third and final release candidate was published a few days ago).

This PR adds Python 3.13 to the tox test suite and to CI.

[coveralls]

coverage: 64.913% (+3.1%) from 61.833%
when pulling 878c408 on kurtmckee:support-python-3.13
into 0f335b3 on LudovicRousseau:master.

[LudovicRousseau]

Please, copy the PR description in the commit message.

[kurtmckee]

I added the text "This PR adds Python 3.13 to the tox test suite and to CI."; if you want the temporal information about the Python 3.13rc3 release a few days ago and the final 3.13.0 release coming in a few days, I can add that.

If you choose to merge the commits using the GitHub interface here, by default the merge commit will include the PR number, which helps create traceability.

[LudovicRousseau]

Yes, using the github merge feature is nice.
I would like to have a really documented commit. In 10 years when github.com will be down I want to be able to know WHY I merged the patch. So I need to have the documentation in the commit message, not just in the PR description.

10 years ago I often used to add links to mailing list archives in my patch messages. But now that the mailing list archives server is down or has moved to a new domain name the links are dead :-(.
A link to a github PR is not a valid long term solution. The description of the WHY has to be in the commit message.

So, yes, you can add more temporal information about the release of Python 3.13. That would explain why you added allow-prereleases: true in the commit.

[kurtmckee]

Makes sense. I'll get this updated.

[LudovicRousseau]

Thanks

[LudovicRousseau]

I used github "rebase and merge" and the PR reference is NOT included.
So it is very important to have all the details in the commit message itself.

I do not like "Create a merge commit" as it make the git log history less linear.

[kurtmckee]

I do not like "Create a merge commit" as it make the git log history less linear.

There are technical disadvantages to linear commit histories. For example, GPG signatures attached to commits are discarded:

Original commit

Transformed commit

As I said before, I'll submit commits with all relevant text in the commit message, but I wanted to bring this technical disadvantage to your attention in case you weren't already aware of it.

[LudovicRousseau]

Very good point.
I had not noticed your commits where GPG signed.
I will create merge commits now.

[kurtmckee]

Thank you for your consideration!