All Versions
33
Latest Version
Avg Release Cycle
50 days
Latest Release
81 days ago

Changelog History
Page 1

  • v21.8.0 Changes

    August 05, 2021

    🔋 Features

    • ⚡️ Update the embedded c-ares from 1.16.1 to 1.17.1. See :issue:1758.
    • ➕ Add support for Python 3.10rc1 and newer.

    As part of this, the minimum required greenlet version was increased to 1.1.0 (on CPython), and the minimum version of Cython needed to build gevent from a source checkout is 3.0a9.

    Note that the dnspython resolver is not available on Python 3.10. See :issue:1790.

    • ⚡️ Update from Cython 3.0a6 to 3.0a9. See :issue:1801.

    Misc

    • 👀 See :issue:1789.

  • v21.1.2 Changes

    January 20, 2021

    🔋 Features

    • ⚡️ Update the embedded libev from 4.31 to 4.33. See :issue:1754.
    • ⚡️ Update the embedded libuv from 1.38.0 to 1.40.0. See :issue:1755.

    Misc

    • 👀 See :issue:1753.

  • v21.1.1 Changes

    January 18, 2021

    🛠 Bugfixes

    🛠 Fix a TypeError on startup on Python 2 with zope.schema installed. Reported by Josh Zuech.

  • v21.1.0 Changes

    January 15, 2021

    🛠 Bugfixes

    • 👉 Make gevent FileObjects more closely match the semantics of native file objects for the name attribute:

      • Objects opened from a file descriptor integer have that integer as their name. (Note that this is the Python 3 semantics; Python 2 native file objects returned from os.fdopen() have the string "" as their name , but here gevent always follows Python 3.)
      • The name remains accessible after the file object is closed.

    Thanks to Dan Milon. See :issue:1745.

    Misc

    ⚠ Make gevent.event.AsyncResult print a warning when it detects improper cross-thread usage instead of hanging.

    AsyncResult has never been safe to use from multiple threads. It, like most gevent objects, is intended to work with greenlets from a single thread. Using AsyncResult from multiple threads has undefined semantics. The safest way to communicate between threads is using an event loop async watcher.

    Those undefined semantics changed in recent gevent versions, making it more likely that an abused AsyncResult would misbehave in ways that could cause the program to hang.

    Now, when AsyncResult detects a situation that would hang, it ⚠ prints a warning to stderr. Note that this is best-effort, and hangs are still possible, especially under PyPy 7.3.3.

    At the same time, AsyncResult is tuned to behave more like it did in older versions, meaning that the hang is once again much less likely. If you were getting lucky and using AsyncResult ⏪ successfully across threads, this may restore your luck. In addition, cross-thread wakeups are faster. Note that the gevent hub now uses an extra file descriptor to implement this.

    👀 Similar changes apply to gevent.event.Event (see :issue:1735).

    👀 See :issue:1739.

  • v20.12.1 Changes

    December 27, 2020

    🔋 Features

    • 👉 Make :class:gevent.Greenlet objects function as context managers. When the with suite finishes, execution doesn't continue until the greenlet is finished. This can be a simpler alternative to a :class:gevent.pool.Group when the lifetime of greenlets can be lexically scoped.

    Suggested by André Caron. See :issue:1324.

    🛠 Bugfixes

    • 👉 Make gevent's Semaphore objects properly handle native thread identifiers larger than can be stored in a C long on Python 3, instead of raising an OverflowError.

    Reported by TheYOSH. See :issue:1733.

  • v20.12.0 Changes

    December 22, 2020

    🔋 Features

    • 👷 Make worker threads created by :class:gevent.threadpool.ThreadPool install the :func:threading.setprofile and :func:threading.settrace hooks while tasks are running. This provides visibility to profiling and tracing tools like yappi.

    Reported by Suhail Muhammed. See :issue:1678.

    • ⬇️ Drop support for Python 3.5.

    🛠 Bugfixes

    • Incorrectly passing an exception instance instead of an exception type to gevent.Greenlet.kill or gevent.killall no longer prints an exception to stderr. See :issue:1663.
    • 👉 Make destroying a hub try harder to more forcibly stop loop processing when there are outstanding callbacks or IO operations scheduled.

    Thanks to Josh Snyder (:issue:1686) and Jan-Philip Gehrcke (:issue:1669). See :issue:1686.

    • 👌 Improve the ability to use monkey-patched locks, and gevent.lock.BoundedSemaphore, across threads, especially when the various threads might not have a gevent hub or any other active greenlets. In particular, this handles some cases that previously raised LoopExit or would hang. Note that this may not be reliable on PyPy on Windows; such an environment is not currently recommended.

    The semaphore tries to avoid creating a hub if it seems unnecessary, automatically creating one in the single-threaded case when it would block, but not in the multi-threaded case. While the differences should be correctly detected, it's possible there are corner cases where they might not be.

    If your application appears to hang acquiring semaphores, but adding a call to gevent.get_hub() in the thread attempting to acquire the semaphore before doing so fixes it, please file an issue. See :issue:1698.

    • 👉 Make error reporting when a greenlet suffers a RecursionError more reliable.

    Reported by Dan Milon. See :issue:1704.

    • 🖨 gevent.pywsgi: Avoid printing an extra traceback ("TypeError: not enough arguments for format string") to standard error on certain invalid client requests.

    Reported by Steven Grimm. See :issue:1708.

    • ➕ Add support for PyPy2 7.3.3. See :issue:1709.
    • Python 2: Make gevent.subprocess.Popen.stdin objects have a write method that guarantees to write the entire argument in binary, unbuffered mode. This may require multiple trips around the event loop, but more closely matches the behaviour of the Python 2 standard library (and gevent prior to 1.5). The number of bytes written is still returned (instead of None). See :issue:1711.
    • 👉 Make gevent.pywsgi stop trying to enforce the rules for reading chunked input or Content-Length terminated input when the connection is being upgraded, for example to a websocket connection. Likewise, if the protocol was switched by returning a 101 status, stop trying to automatically chunk the responses.

    Reported by Kavindu Santhusa. See :issue:1712.

    • Remove the __dict__ attribute from gevent.socket.socket objects. The standard library socket do not have a __dict__.

    Noticed by Carson Ip.

    As part of this refactoring, share more common socket code between Python 2 and Python 3. See :issue:1724.

  • v20.9.0 Changes

    September 22, 2020

    🔋 Features

    • The embedded libev is now asked to detect the availability of clock_gettime and use the realtime and/or monotonic clocks, if they are available.

    On Linux, this can reduce the number of system calls libev makes. Originally provided by Josh Snyder. See :issue:issue1648.

    🛠 Bugfixes

    • On CPython, depend on greenlet >= 0.4.17. This version is binary incompatible with earlier releases on CPython 3.7 and later.

    On Python 3.7 and above, the module gevent.contextvars is no longer monkey-patched into the standard library. contextvars are now both greenlet and asyncio task local. See :issue:1656. See :issue:issue1674.

    • The DummyThread objects created automatically by certain operations when the standard library threading module is monkey-patched now match the naming convention the standard library uses ("Dummy-12345"). Previously (since gevent 1.2a2) they used "DummyThread-12345". See :issue:1659.
    • 🛠 Fix compatibility with dnspython 2.

    .. caution:: This currently means that it can be imported. But it cannot yet be used. gevent has a pinned dependency on dnspython < 2 for now. See :issue:1661.

  • v20.6.2 Changes

    June 16, 2020

    🔋 Features

    • 🏗 It is now possible to build and use the embedded libuv on a Cygwin platform.

    Note that Cygwin is not an officially supported platform of upstream libuv and is not tested by gevent, so the actual working status is unknown, and this may bitrot in future releases.

    Thanks to berkakinci for the patch. See :issue:issue1645.

    🛠 Bugfixes

    • 😌 Relax the version constraint for psutil on PyPy.

    Previously it was pinned to 5.6.3 for PyPy2, except for on Windows, where it was excluded. It is now treated the same as CPython again. See :issue:issue1643.

  • v20.6.1 Changes

    June 10, 2020

    🔋 Features

    • ⬆️ gevent's CI is now tested on Ubuntu 18.04 (Bionic), an upgrade from 16.04 (Xenial). See :issue:1623.

    🛠 Bugfixes

    • On Python 2, the dnspython resolver can be used without having selectors2 installed. Previously, an ImportError would be raised. See :issue:issue1641.
    • Python 3 gevent.ssl.SSLSocket objects no longer attempt to catch ConnectionResetError and treat it the same as an SSLError with SSL_ERROR_EOF (typically by suppressing it).

    This was a difference from the way the standard library behaved (which is to raise the exception). It was added to gevent during early testing of OpenSSL 1.1 and TLS 1.3. See :issue:1637.

  • v20.6.0 Changes

    June 06, 2020

    🔋 Features

    • ➕ Add gevent.selectors containing GeventSelector. This selector implementation uses gevent details to attempt to reduce overhead when polling many file descriptors, only some of which become ready at any given time.

    This is monkey-patched as selectors.DefaultSelector by default.

    This is available on Python 2 if the selectors2 backport is installed. (This backport is installed automatically using the recommended extra.) When monkey-patching, selectors is made available as an alias to this module. See :issue:1532.

    • Depend on greenlet >= 0.4.16. This is required for CPython 3.9 and 3.10a0. See :issue:1627.
    • ➕ Add support for Python 3.9.

    No binary wheels are available yet, however. See :issue:1628.

    🛠 Bugfixes

    • gevent.socket.create_connection and gevent.socket.socket.connect no longer ignore IPv6 scope IDs.

    Any IP address (IPv4 or IPv6) is no longer subject to an extra call to getaddrinfo. Depending on the resolver in use, this is likely to change the number and order of greenlet switches. (On Windows, in particular test cases when there are no other greenlets running, it has been observed to lead to LoopExit in scenarios that didn't produce that before.) See :issue:1634.