[Python-Dev] [PEP 3148] futures - execute computations asynchronously
Daniel Stutzbach
daniel at stutzbachenterprises.com
Fri Mar 5 18:28:42 CET 2010
On Fri, Mar 5, 2010 at 11:03 AM, Jesse Noller <jnoller at gmail.com> wrote:
> http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html
>
According to that link, Java has a module named "Concurrent" with an
interface named "Future". You're proposing a module named "Futures" with a
class named "Future".
Why not name your module "concurrent"? That would eliminate the confusion
with "from __future__". I don't see a problem with keeping the class name.
Plus, a "concurrent" module might be useful for things other than Futures,
in the future. ;-)
Just my 0.02 cents,
--
Daniel Stutzbach, Ph.D.
President, Stutzbach Enterprises, LLC <http://stutzbachenterprises.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100305/db13a15d/attachment.html>
More information about the Python-Dev
mailing list