pep-550: Fix typos (#330)
This commit is contained in:
parent
b96cdf5fbb
commit
f7c4d9603e
11
pep-0550.rst
11
pep-0550.rst
|
@ -669,14 +669,13 @@ Generators and Coroutines
|
|||
-------------------------
|
||||
|
||||
Using a microbenchmark for generators and coroutines from :pep:`492`
|
||||
([12]_), it was possible to observe 0.5 to 1% performance degradation
|
||||
for generators and coroutines.
|
||||
([12]_), it was possible to observe 0.5 to 1% performance degradation.
|
||||
|
||||
asyncio echoserver microbechmarks from the uvloop project [13]_
|
||||
showed 1-1.5% performance degradation for asyncio code.
|
||||
|
||||
asyncpg benchmarks [14]_, that execute more code and closer to a
|
||||
real-world application did not exhibit any detectable performance
|
||||
asyncpg benchmarks [14]_, that execute more code and are closer to a
|
||||
real-world application did not exhibit any noticeable performance
|
||||
change.
|
||||
|
||||
|
||||
|
@ -922,6 +921,7 @@ This allows to implement context managers like decimal context and
|
|||
The following code::
|
||||
|
||||
class Context:
|
||||
|
||||
def __enter__(self):
|
||||
self.old_x = get_execution_context_item('x')
|
||||
set_execution_context_item('x', 'something')
|
||||
|
@ -932,6 +932,7 @@ The following code::
|
|||
would become this::
|
||||
|
||||
class Context:
|
||||
|
||||
def __enter__(self):
|
||||
self.old_x = get_execution_context_item('x')
|
||||
set_execution_context_item('x', 'something')
|
||||
|
@ -960,7 +961,7 @@ Can Execution Context be implemented outside of CPython?
|
|||
--------------------------------------------------------
|
||||
|
||||
Because async/await code needs an event loop to run it, an EC-like
|
||||
solution canbe implemented in a limited way for coroutines.
|
||||
solution can be implemented in a limited way for coroutines.
|
||||
|
||||
Generators, on the other hand, do not have an event loop or
|
||||
trampoline, making it impossible to intercept their ``yield`` points
|
||||
|
|
Loading…
Reference in New Issue