python-gevent
No description set
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
12
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:zSystems/python-gevent && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
fix-no-return-in-nonvoid-function.patch | 0000000616 616 Bytes | |
gevent-23.9.0.tar.gz | 0004027348 3.84 MB | |
python-gevent-rpmlintrc | 0000000092 92 Bytes | |
python-gevent.changes | 0000088195 86.1 KB | |
python-gevent.spec | 0000006327 6.18 KB |
Revision 45 (latest revision is 51)
Ana Guerrero (anag+factory)
accepted
request 1112068
from
Dirk Mueller (dirkmueller)
(revision 45)
- update to 23.9.0 (CVE-2023-41419): * Make ``gevent.select.select`` accept arbitrary iterables, not just sequences. That is, you can now pass in a generator of file descriptors instead of a realized list. Internally, arbitrary iterables are copied into lists. This better matches what the standard library does. * On Python 3.11 and newer, opt out of Cython's fast exception manipulation, which *may* be causing problems in certain circumstances when combined with greenlets. * On all versions of Python, adjust some error handling in the default * -based loop. This fixes several assertion failures on debug versions of CPython. Hopefully it has a positive impact under real conditions. * Make ``gevent.pywsgi`` comply more closely with the HTTP specification for chunked transfer encoding. In particular, we are much stricter about trailers, and trailers that are invalid (too long or featuring disallowed characters) forcibly close the connection to the client *after* the results have been sent. * Trailers otherwise continue to be ignored and are not available to the WSGI application. Previously, carefully crafted invalid trailers in chunked requests on keep-alive connections might appear as two requests to ``gevent.pywsgi``. Because this was handled exactly as a normal keep-alive connection with two requests, the WSGI application should handle it normally. However, if you were counting on some upstream server to filter incoming requests based on paths or header fields, and the upstream server simply passed trailers through without validating them, then this embedded second request would
Comments 0