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 geertj, giampaolo.rodola, gvanrossum, pitrou, sbt, vstinner, yselivanov
Date 2014-10-06.02:13:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This is awesome news!

Since this is 3.5 only, I guess this means the end of my attempts to keep the asyncio source code identical in the Tulip repo (from which I occasionally create builds that work with Python 3.3) and in the 3.4 and 3.5 branches.  I guess that's okay, people should be switching to 3.5 anyway.  I'm not sure what approach to follow to keep the branches at least somewhat in sync -- perhaps tulip and 3.4 can still be kept identical, with changes merged from 3.4 into 3.5 (default) but 3.5 differing in some places?  Or perhaps the code can be kept identical with the exception of the file, and conditional import of the latter?
Date User Action Args
2014-10-06 02:13:24gvanrossumsetrecipients: + gvanrossum, geertj, pitrou, vstinner, giampaolo.rodola, sbt, yselivanov
2014-10-06 02:13:24gvanrossumsetmessageid: <>
2014-10-06 02:13:24gvanrossumlinkissue22560 messages
2014-10-06 02:13:24gvanrossumcreate