➜

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 vstinner
Recipients gvanrossum, larry, vajrasky, vstinner, yselivanov
Date 2014-02-20.08:06:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392883593.72.0.733921633737.issue20648@psf.upfronthosting.co.za>
In-reply-to
Content 
> Should these be cherry-picked too?

We discuss with Guido and Yury to only include "critical" changes, so in short: yes, all commits related to asyncio should be cherrry-picked into RC2. It should also be easier for you to include all changes, to avoid conflicts. And the code should be the same in default and RC2 for asyncio.
History
Date User Action Args
2014-02-20 08:06:33vstinnersetrecipients: + vstinner, gvanrossum, larry, yselivanov, vajrasky
2014-02-20 08:06:33vstinnersetmessageid: <1392883593.72.0.733921633737.issue20648@psf.upfronthosting.co.za>
2014-02-20 08:06:33vstinnerlinkissue20648 messages
2014-02-20 08:06:33vstinnercreate