This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients barry, giampaolo.rodola, njs, pitrou, vstinner, yselivanov
Date 2017-05-30.23:55:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20170530195516.0c41903e@subdivisions.wooz.org>
In-reply-to <61408F3C-4B42-4466-A4B6-7E9F039D5D71@gmail.com>
Content
On May 30, 2017, at 10:36 PM, Yury Selivanov wrote:

>Again, the natural way of something like Controller to end up in asyncio is
>to either go through full PEP process, or live some time on PyPI and prove to
>be useful.

A PEP feels like overkill; we don't require PEPs for every addition to an
existing stdlib module or package.  My worry too is that a PEP tends to evoke
endless bikeshedding.

I appreciate that you want to be careful not to saddle asyncio with too much
baggage, or that you don't feel Controller is significant enough to generalize
and put in the package.  Perhaps a middle ground would be to label parts of
the asyncio API provisional, and add Controller to that?
History
Date User Action Args
2017-05-30 23:55:19barrysetrecipients: + barry, pitrou, vstinner, giampaolo.rodola, njs, yselivanov
2017-05-30 23:55:19barrylinkissue30300 messages
2017-05-30 23:55:19barrycreate