pep-0492: New Abstract section; thanks to Elvis Pranskevichus.
This commit is contained in:
parent
384743cdef
commit
0ee58b260f
20
pep-0492.txt
20
pep-0492.txt
|
@ -14,10 +14,22 @@ Post-History: 17-Apr-2015, 21-Apr-2015, 27-Apr-2015, 29-Apr-2015
|
|||
Abstract
|
||||
========
|
||||
|
||||
This PEP introduces new syntax for coroutines, asynchronous ``with``
|
||||
statements and ``for`` loops. The main motivation behind this proposal
|
||||
is to streamline writing and maintaining asynchronous code, as well as
|
||||
to simplify previously hard to implement code patterns.
|
||||
The growth of Internet and general connectivity has triggered the
|
||||
proportionate need for responsive and scalable code. This proposal
|
||||
aims to answer that need by making writing explicitly asynchronous,
|
||||
concurrent Python code easier and more Pythonic.
|
||||
|
||||
It is proposed to make *coroutines* a proper standalone concept in
|
||||
Python, and introduce new supporting syntax. The ultimate goal
|
||||
is to help establish a common, easily approachable, mental
|
||||
model of asynchronous programming in Python and make it as close to
|
||||
synchronous programming as possible.
|
||||
|
||||
This PEP improves upon PEP 342, and, in a sense, supercedes it. We
|
||||
believe that the changes proposed here will help keep Python
|
||||
relevant and competitive in a quickly growing area of asynchronous
|
||||
programming, as many other languages have adopted, or are planning to
|
||||
adopt, similar features: [2]_, [5]_, [6]_, [7]_, [8]_, [10]_.
|
||||
|
||||
|
||||
Rationale and Goals
|
||||
|
|
Loading…
Reference in New Issue