delta/python-packages/eventlet.git, branch master

tests: getaddrinfo(host, 0) is not supported on OpenIndiana platform

2023-03-27T19:07:15+00:00

https://github.com/eventlet/eventlet/issues/791

dep: greenlet>=1.0 removing unused clear_sys_exc_info stub

2023-03-27T16:16:48+00:00

fixes https://github.com/eventlet/eventlet/issues/763

build: include tox.ini and repo docs in PyPI package

2023-03-01T07:10:17+00:00

fixes https://github.com/eventlet/eventlet/issues/790

wsgi: Allow keepalive option to be a timeout

2023-02-22T20:04:01+00:00

Sometimes the server pool fills up; all max_size greenthreads are
already in use with other connections. One more connection gets
accept()ed, but then has to wait for a slot to open up to actually be
handled.

This works out fine if your clients tend to make a single request then
close the connection upon receiving a response. It works out OK-ish when
clients are continually pipelining requests; the new connection still
has to wait, but at least there's plenty of work getting processed --
it's defensible. It can work out pretty terribly if clients tend to hold
on to connections "just in case" -- we're ignoring fresh work from a new
client just so we can be ready-to-go if an existing connection wakes up.

There are a couple existing tunings we can use, but they can each have
downsides:

- Increasing max_size is nice for dealing with idle connections, but can
  cause hub contention and high latency variance when all those
  connections are actually busy.
- socket_timeout can be used to limit the idle socket time, but it
  *also* impacts send/recv operations while processing a request, which
  may not be desirable.
- keepalive can be set to False, disabling request pipelining entirely.

Change the keepalive option to wsgi.server so it can be the timeout to
use while waiting for a new request, separate from socket_timeout. By
default, socket_timeout continues to be used.

dns: support host as bytes in getaddrinfo, resolve

2023-02-02T02:00:37+00:00

Relevant traceback:

```
  File "dns/resolver.py", line 858, in query
    if qname.is_absolute():
AttributeError: 'bytes' object has no attribute 'is_absolute'
```

Fixes https://github.com/eventlet/eventlet/issues/599

Co-authored-by: Sergey Shepelev 
Co-authored-by: Tim Burke

green.http: collections.Iterable alias removed in Python 3.10, CI 3.10, drop non-essential CI against 2.7 to 3.6

2023-01-22T04:35:32+00:00

fixes https://github.com/eventlet/eventlet/issues/740

related to https://github.com/eventlet/eventlet/pull/715

hubs: drop pyevent hub

2023-01-22T00:26:31+00:00

https://github.com/eventlet/eventlet/pull/657

doc: fix sys.path for shared sphinx-build

2023-01-20T16:33:09+00:00

https://github.com/eventlet/eventlet/issues/785

Signed-off-by: Sergey Shepelev

chore: CI upgrades, pycodestyle fix 2 empty lines after class/def

2023-01-18T05:55:02+00:00

- github actions ubuntu-latest switched to 22.04 with python3>=3.7
- tool: pep8 was renamed and upgraded to pycodestyle 2.1, fixed 2 empty lines after class/def
- common github actions upgrade to v3 https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

Change ssl to return a socket.timeout exception on timeout instead of an SSLError

2023-01-18T01:02:49+00:00

Back in Python 3.2, ssl.SSLError used to be a subclass of socket.error (see
https://docs.python.org/3/library/ssl.html#exceptions), so timeouts on
monkeypatched ssl sockets would be properly caught by socket.timeout
excpetion handlers in applications.  However, since Python 3.3 ssl.SSLerror
is a subclass of OSError, which signifies a different (typically fatal)
type of error that is usually not handled gracefully by applications.

By changing the timeout excpetion back to socket.timeout, libraries such
as pymysql and redis will again properly support TLS-connections in
monkeypatched apoplications.