Re: [Python-Dev] Making PEP 3156 (asyncio) non-provisional

2016-09-07 Thread Guido van Rossum
On Wed, Sep 7, 2016 at 8:43 PM, Nick Coghlan wrote: > On 8 September 2016 at 04:31, Guido van Rossum wrote: >> There's also the issue of starttls, a feature that we know we'd like >> to add but don't have ready for 3.6b1. I think the right approach >> there is to provide an add-on package on PyPI

Re: [Python-Dev] Making PEP 3156 (asyncio) non-provisional

2016-09-07 Thread Nick Coghlan
On 8 September 2016 at 04:31, Guido van Rossum wrote: > There's also the issue of starttls, a feature that we know we'd like > to add but don't have ready for 3.6b1. I think the right approach > there is to provide an add-on package on PyPI that implements a > starttls-capable Transport class, and

[Python-Dev] Making PEP 3156 (asyncio) non-provisional

2016-09-07 Thread Guido van Rossum
PEP 3156 and the asyncio module it defines have been provisional for the lifetime of Python 3.4 and 3.5. The module is now quite mature. I propose that we end the provisional period and make asyncio subject to the usual backwards compatibility rules: new features only appear in "minor" releases (e.