iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

pep 525: We don't have a hard requirement for finalizers anymore

This commit is contained in:
Yury Selivanov 2016-12-08 13:29:38 -08:00
parent 6b94a13802
commit 3e23210fe3
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pep-0525.txt
View File

@ -215,13 +215,10 @@ problem, and everything just works.
generator is about to be GCed. generator is about to be GCed.
When an asynchronous generator is iterated for the first time, When an asynchronous generator is iterated for the first time,
it stores a reference to the current finalizer. If there is none, it stores a reference to the current *finalizer*.
a ``RuntimeError`` is raised. This provides a strong guarantee that
every asynchronous generator object will always have a finalizer
installed by the correct event loop.
When an asynchronous generator is about to be garbage collected, When an asynchronous generator is about to be garbage collected,
it calls its cached finalizer. The assumption is that the finalizer it calls its cached *finalizer*. The assumption is that the finalizer
will schedule an ``aclose()`` call with the loop that was active will schedule an ``aclose()`` call with the loop that was active
when the iteration started. when the iteration started.