➜

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 gvanrossum
Recipients gvanrossum, larry, vstinner, yselivanov
Date 2014-02-17.00:09:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJKNcvfcbxUb+Sk=3hPkvtFWtUPyG3v5d8RCmGagG5WwVA@mail.gmail.com>
In-reply-to <1392595186.22.0.679105345844.issue20648@psf.upfronthosting.co.za>
Content 
Right, that has been my understanding. Larry has said he'd give asyncio a
generous exception because it's all new in 3.4.

On Sunday, February 16, 2014, Yury Selivanov <report@bugs.python.org> wrote:

>
> Yury Selivanov added the comment:
>
> I think we should just ask Larry to merge all commits for asyncio in 3.4.
> I.e. we won't commit anything that should not go in 3.4 anyways.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org <javascript:;>>
> <http://bugs.python.org/issue20648>
> _______________________________________
>
History
Date User Action Args
2014-02-17 00:09:56gvanrossumsetrecipients: + gvanrossum, vstinner, larry, yselivanov
2014-02-17 00:09:56gvanrossumlinkissue20648 messages
2014-02-17 00:09:56gvanrossumcreate