<br><br><div class="gmail_quote">On Fri, Mar 5, 2010 at 09:55, Jesse Noller <span dir="ltr"><<a href="mailto:jnoller@gmail.com">jnoller@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Mar 5, 2010 at 12:28 PM, Daniel Stutzbach<br>
<<a href="mailto:daniel@stutzbachenterprises.com">daniel@stutzbachenterprises.com</a>> wrote:<br>
> On Fri, Mar 5, 2010 at 11:03 AM, Jesse Noller <<a href="mailto:jnoller@gmail.com">jnoller@gmail.com</a>> wrote:<br>
>><br>
>> <a href="http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html" target="_blank">http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html</a><br>
><br>
> According to that link, Java has a module named "Concurrent" with an<br>
> interface named "Future". You're proposing a module named "Futures" with a<br>
> class named "Future".<br>
><br>
> Why not name your module "concurrent"? That would eliminate the confusion<br>
> with "from __future__". I don't see a problem with keeping the class name.<br>
><br>
> Plus, a "concurrent" module might be useful for things other than Futures,<br>
> in the future. ;-)<br>
><br>
<br>
</div>Brian's module is named futures; I am +1'ing his proposal, and also<br>
suggesting we put it under concurrent/ package name. This means you<br>
would do the following:<br>
<br>
from concurrent import futures<br>
<br>
and in the future:<br>
from concurrent import pool<br>
<br>
And so on.</blockquote><div><br></div><div><br></div><div>So I don't quite get what you are after here. Are you wanting to eventually have a generic pool class that you can simply import and use that is always set to the best option for the platform?</div>
<div><br></div><div>And as for moving stuff from multiprocessing into the concurrent namespace, are you thinking like concurrent.multiprocessing? I guess I am just trying to figure out what the abstraction is you are after in the package namespace.</div>
<div><br></div><div>-Brett</div></div>