RetroSearch Browse

Mon Sep 30 01:51:58 CEST 2013 · https://mail.python.org/pipermail/python-dev/2013-September/129077.html

On 09/27/2013 11:33 PM, Guido van Rossum wrote:
> I've been looking at my progress with Tulip and the 3.4 release 
> schedule (PEP 429) and it looks like I will have to do some kind of 
> sprint to get it into the release in time for beta 1, which is planned 
> for Nov 24. Ideally I'd get it into alpha 4, which is scheduled for 
> Oct 20 -- that's in about three weeks, and probably too tight.
>
> Even Nov 24 is aggressive, because the PEP (PEP 3156) hasn't even been 
> discussed formally, let alone accepted! Fortunately I'm pretty happy 
> with most of the APIs defined in the PEP -- there are some holes but I 
> expect no big changes at this point.

My guess is, a lot of people would be disappointed if Tulip missed 3.4.  
I suspect the community would rather we slip the beta a little if it 
meant it the difference between Tulip and no Tulip.  I just hope you 
make it easy on me and beat the deadline ;-)

Cheers,

//arry/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20130930/45defbb1/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-September/129077.html below:

[Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio