doc/source/modules/zmq.rst | 1 0 + 1 - 0 !
1 file changed, 1 deletion(-)

 removes line that is doing ftbfs in doc

examples/websocket.html | 4 2 + 2 - 0 !
examples/websocket_chat.html | 2 1 + 1 - 0 !
2 files changed, 3 insertions(+), 3 deletions(-)

 fixed privacy breach in examples

 Upstream is referencing external websites, we don't allow this.

tests/zmq_test.py | 6 3 + 3 - 0 !
1 file changed, 3 insertions(+), 3 deletions(-)

 allow more busy cpu

 The tests assume a fast CPU, but under my VMs, the tests are just failing
 with the CPU being more than 10% busy.

tests/greenio_test.py | 20 0 + 20 - 0 !
tests/socket_test.py | 7 0 + 7 - 0 !
2 files changed, 27 deletions(-)

 remove networking tests

 Upstream is attempting connection to 192.0.2.1 on port 80, and expects
 it to always timeout. However, some Debian users may well have a web
 server running on that IP address, meaning the test would fail in such
 setup (even if this is reserved IANA IPs). Therefore, removing such bad
 tests.
 .
 Also, these tests have been failing for a reason on my arm64 builder,
 probably because it's a slow machine.

tests/patcher_test.py | 3 0 + 3 - 0 !
1 file changed, 3 deletions(-)

 removed failing test

 This test fails in Sid.

doc/source/conf.py | 1 0 + 1 - 0 !
1 file changed, 1 deletion(-)

 patch out intersphinx
 Avoids internet access during build

tests/wsgi_test.py | 12 6 + 6 - 0 !
1 file changed, 6 insertions(+), 6 deletions(-)

 disable test_server_connection_timeout_exception()

 As per the bug report, the test is non-deterministic. Therefore,
 remove it it.
Bug-Debian: https://bugs.debian.org/857893

tests/subprocess_test.py | 20 0 + 20 - 0 !
1 file changed, 20 deletions(-)

 remove non-deterministic test_communicate_with_poll()
 This patch fails sometimes, which isn't acceptable in Debian, so I'm
 removing it to avoid issues.

tests/wsgi_test.py | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 <short summary of the patch>
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 python-eventlet (0.33.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Uploading to unstable.
   * Run unit tests at build time.
   * Add py310-Fix-_fix_py3_rlock.patch (Closes: #1009112).

tests/patcher_test.py | 4 0 + 4 - 0 !
1 file changed, 4 deletions(-)

 remove test_patcher_existing_locks_locked()
 This is a temporary solution until a better patch can be written, which
 is currently too much for my skills.

tests/wsgi_test.py | 3 0 + 3 - 0 !
1 file changed, 3 deletions(-)

 neutralize test_017_ssl_zeroreturnerror()
 This fails.

MANIFEST.in | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 install all files

pyproject.toml | 7 2 + 5 - 0 !
1 file changed, 2 insertions(+), 5 deletions(-)

 fix detecting version

.github/workflows/test.yaml | 31 17 + 14 - 0 !
README.rst | 2 1 + 1 - 0 !
eventlet/green/thread.py | 72 64 + 8 - 0 !
eventlet/green/threading.py | 7 4 + 3 - 0 !
pyproject.toml | 1 1 + 0 - 0 !
tox.ini | 2 1 + 1 - 0 !
6 files changed, 88 insertions(+), 27 deletions(-)

 [patch 1/9] reorder python jobs by python versions
From a79863aaa5b63b3d1e3fd4bfcb2f7c6f41770dfe Mon Sep 17 00:00:00 2001

eventlet/debug.py | 8 6 + 2 - 0 !
tests/debug_test.py | 4 3 + 1 - 0 !
2 files changed, 9 insertions(+), 3 deletions(-)

 spew: correct line lookup from inspect.getsourcelines()
 I can't write a test for this, as I don't know how to trigger is part of
 Spew, without also falling into the OSError branch (which
 test_line_nofile tests).
 .
 However, it has been observed to hit this code when running the tests
 under pytest-xdist (execnext), and the code is obviously wrong. This
 corrects it.

eventlet/green/thread.py | 2 2 + 0 - 0 !
tests/isolated/patcher_threading_subclass_done.py | 40 40 + 0 - 0 !
tests/patcher_test.py | 4 4 + 0 - 0 !
3 files changed, 46 insertions(+)

 python 3.13: use greenthread's dead state where possible
Fixes: #998