Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gevent
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
gevent
Commits
94e52b13
Commit
94e52b13
authored
Jan 15, 2021
by
Jason Madden
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Preparing release 21.1.0
parent
d54515c1
Changes
6
Hide whitespace changes
Inline
Side-by-side
Showing
6 changed files
with
58 additions
and
38 deletions
+58
-38
CHANGES.rst
CHANGES.rst
+55
-0
docs/changes/1739.misc
docs/changes/1739.misc
+0
-25
docs/changes/1745.bugfix
docs/changes/1745.bugfix
+0
-10
src/gevent/__init__.py
src/gevent/__init__.py
+1
-1
src/gevent/_interfaces.py
src/gevent/_interfaces.py
+1
-1
src/gevent/monkey.py
src/gevent/monkey.py
+1
-1
No files found.
CHANGES.rst
View file @
94e52b13
...
...
@@ -6,6 +6,61 @@
.. towncrier release notes start
21.1.0 (2021-01-15)
===================
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
"<fdopen>" 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`.
----
20.12.1 (2020-12-27)
====================
...
...
docs/changes/1739.misc
deleted
100644 → 0
View file @
d54515c1
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`).
docs/changes/1745.bugfix
deleted
100644 → 0
View file @
d54515c1
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
"<fdopen>" as their name , but here gevent always follows Python 3.)
- The ``name`` remains accessible after the file object is closed.
Thanks to Dan Milon.
src/gevent/__init__.py
View file @
94e52b13
...
...
@@ -27,7 +27,7 @@ version_info = _version_info(20, 0, 0, 'dev', 0) # XXX: Remove me
#: Use ``pkg_resources.parse_version(__version__)`` or
#: ``packaging.version.Version(__version__)`` to get a machine-usable
#: value.
__version__
=
'2
0.12.2.dev
0'
__version__
=
'2
1.1.
0'
__all__
=
[
...
...
src/gevent/_interfaces.py
View file @
94e52b13
...
...
@@ -243,7 +243,7 @@ class ILoop(Interface):
loop to notice that the *func* has been scheduled (e.g., it causes
the loop to wake up).
.. versionadded::
NEXT
.. versionadded::
21.1.0
.. seealso:: :meth:`asyncio.loop.call_soon_threadsafe`
The :mod:`asyncio` equivalent.
...
...
src/gevent/monkey.py
View file @
94e52b13
...
...
@@ -239,7 +239,7 @@ def is_anything_patched():
# it is 100% reliable in the event of third-party patch functions that
# don't use ``saved``.
#
# .. versionadded::
NEXT
# .. versionadded::
21.1.0
return
bool
(
saved
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment