fix: avoid bug in various patch releases of Python

[henryiii]

Fix #674. Serious enough that we should get a patch release out imo.

[Secrus]

Would be nice to get this merged and released, so package managers can use patched version :)

[layday]

https://docs.python.org/release/3.10.13/whatsnew/changelog.html#library

[layday]

@encukou Sorry to bother you, but would you be able to please verify the above version numbers?

[gaborbernat]

[encukou]

Confirmed. Thank you, and sorry for the trouble!

If another project wants to copy this approach: you could instead add and sys.version_info[:3] not in {(3, 8, 18), (3, 9, 18), (3, 10, 13), (3, 11, 5)}, (edit: see correction below) to allow builds of old Python with the feature backported.

[effigies]

Thanks all!

[dimbleby]

If another project wants to copy this approach: you could instead add and sys.version_info[:3] not in {(3, 8, 18), (3, 9, 18), (3, 10, 13), (3, 11, 5)}, to allow builds of old Python with the feature backported.

per the changelogs, that set seems to be the versions at which the fix was made. The correct set of faulty versions should be {(3, 8, 17), (3, 9, 17), (3, 10, 12), (3, 11, 4)}