RetroSearch Browse

Sat Sep 28 19:02:19 CEST 2013 · https://mail.python.org/pipermail/python-dev/2013-September/129062.html

On Sat, Sep 28, 2013 at 9:07 AM, Eli Bendersky <eliben at gmail.com> wrote:
>
>
> Sounds good. But once it's in stdlib, I think it would be proper to shift
> the discussion into the normal pydev channels (python-dev, issue tracker,
> etc.). Is this the plan?
>

Hadn't really thought about that. I think there's a precedent for aspects
of Python that have their own mailing list (e.g. import-sig). Also,
python-dev is usually pretty hostile about people asking usage questions --
there's no such taboo on the Tulip list.

I can certainly see how you wouldn't want to have to look at multiple
trackers. Possibly the Tulip tracker could be limited to discussion of the
Python 3.3 backport that I hope to maintain in that project.

-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20130928/75087793/attachment-0001.html>

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

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

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