[Python-Dev] Moving forward with the concurrent package (original) (raw)
Raymond Hettinger raymond.hettinger at gmail.com
Wed Aug 10 22:46:41 CEST 2011
- Previous message: [Python-Dev] Moving forward with the concurrent package
- Next message: [Python-Dev] Moving forward with the concurrent package
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
Raymond
- Previous message: [Python-Dev] Moving forward with the concurrent package
- Next message: [Python-Dev] Moving forward with the concurrent package
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]