A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-August/112789.html below:

[Python-Dev] Moving forward with the concurrent package

[Python-Dev] Moving forward with the concurrent packageBenjamin Peterson benjamin at python.org
Wed Aug 10 23:37:16 CEST 2011
2011/8/10 Raymond Hettinger <raymond.hettinger at gmail.com>:
>
> On Aug 10, 2011, at 1:36 PM, Antoine Pitrou wrote:
>
>> Le Wed, 10 Aug 2011 14:54:33 -0500,
>> Benjamin Peterson <benjamin at python.org> a écrit :
>>> 2011/8/10 Brian Curtin <brian.curtin at gmail.com>:
>>>> Now that we have concurrent.futures, is there any plan for
>>>> multiprocessing to follow suit? PEP 3148 mentions a hope to add or move
>>>> things in the future
>>>
>>> Is there some sort of concrete proposal? The PEP just seems to mention
>>> it as an idea.
>>>
>>> In general, -1. I think we don't need to be moving things around more
>>> to little advantage.
>>
>> Agreed. Also, flat is better than nested. Whoever wants to populate the
>> concurrent package should work on new features to be added to it, rather
>> than plans to rename things around.
>
> I concur.

So we could put yourself, Antoine, and me in the concurrent package. :)

Sorry,
Benjamin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4