Jason Madden

I am unable to reproduce this on Python 3.13.3 with OpenSSL 3.5.0 on either macOS or Linux (the manylinux 2014 image, in which I manually upgraded OpenSSL). Which specific test...

The logs you provided don't show an error in gevent's `test__server.py`. Instead, they show several errors in the standard library's `test_ssl.py`, all of type `ConnectionRefusedError`. I can indeed reproduce that...

The relevant CPython change appears to be [this one](https://github.com/python/cpython/issues/126500), which appears to only have been backported to 3.12, not 3.11 or older, probably because those versions are either in security-fix-only...

We don't make changes to the standard library tests. We don't backport changes the coredevs don't.

No, we can't just use the tests from some OS provided package. They're an incredibly important part of gevent's test suite and as such must always be available no matter...

Please provide your code snippet.

Noting current status: The Python issue is closed, and has been fixed in 3.12 and 3.13. It won't be fixed in 3.11 because it is in security-fix only mode.

Here's the error: ``` /usr/bin/python3.11 -u -W ignore -m gevent.testing.monkey_test test_socket.py [code TIMEOUT] [took 120.0s] ``` - The test is timing out. Whether this is a legitimate hang or simply...

Interesting. The line in question (443) is a call into Cython-generated native code, so I'm immediately suspicious of a Cython bug. Does the problem go away if you run gevent...

Line ssl.py:437 is not gevent doing anything. We're making a call into the standard library's SSL object, obtained by calling the standard library's `SSLContext._wrap_socket` method, passing it a standard library...