Support Python3.11

[alexrudd2]

Closes #1245.

All tests pass on Python3.11 the same as Python3.10 and 3.8 on MacOS for me.

I see you have simplified and cleaned up the CI a lot; awesome! Hopefully it's easy to add 3.11

[janiversen]

Removing reuse_addr for UDP is a good thing, I thought I had done that already. BUT you cannot remove reuse_addr from TCP, this is highly needed.

[janiversen]

IMPORTANT, please do a "git pull" before making changes, I added a commit changing README.rst

[alexrudd2]

Removing reuse_addr for UDP is a good thing, I thought I had done that already.

You had set it to False, which emitted a DeprecationWarning previously and is now entirely removed in 3.11

BUT you cannot remove reuse_addr from TCP, this is highly needed.

OK, I assume TLS follows TCP. Changed to only UDP.

IMPORTANT, please do a "git pull" before making changes, I added a commit changing README.rst

OK. I rebased and force-pushed.

[janiversen]

LGTM.

I wrote earlier "IMPORTANT, please do a "git pull" before making changes, I added a commit changing README.rst"

You did not do that, but instead did "git push -f" and thus killed my commit. It would have been nice, it you had included the change in your commit, so I avoided doing it twice.

[alexrudd2]

My apologies for not understanding your message, although I didn't ignore it.

I saw you had committed 33659da, which merged dev into my branch. (It's still available with git log) I did not see any relevant README changes that weren't in other commits - the changes present would get dropped by merging this back into dev.

I pulled dev and rebased this branch on top so there were no conflicts, then did git push --force-with-lease. Using this instead of --force means I had was not overwriting any remote commits I had not seen.

Had you encountered a merge conflict? Did I make a mistake in the rebase?

[janiversen]

I did a commit on this branch not dev. I did it directly on dev in the second turn.

I did not encounter a merge conflict my commit was simply gone, due to your “git push —force…” (any version of —force, replaces the commit log for the branch on the server with your version).

You should have done “git pull” before starting to work, then the normal “git push” would have worked. But anyhow it is history now and it was not a big problem, just wanted to mention it.

Looking forward to see more work from you. Let me know if you want ideas of what needs to be done.