RetroSearch Browse

Fri Mar 5 19:30:35 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-March/098187.html

On 05:06 pm, curt at hagenlocher.org wrote:
>On Fri, Mar 5, 2010 at 8:35 AM, Jesse Noller <jnoller at gmail.com> wrote:
>>
>>On Fri, Mar 5, 2010 at 11:21 AM, Daniel Stutzbach
>><daniel at stutzbachenterprises.com> wrote:
>> > On Fri, Mar 5, 2010 at 12:03 AM, Brian Quinlan <brian at sweetapp.com> 
>>wrote:
>> >>
>> >> import futures
>> >
>> > +1 on the idea, -1 on the name.  It's too similar to "from 
>>__future__ import
>> > ...".
>>
>>Futures is a common term for this, and implemented named this in other
>>languages. I don't think we should be adopting things that are common,
>>and found elsewhere and then renaming them.
>
>Another common term for this is a "promise".

Promises aren't exactly the same.  This would be a particularly bad name 
to apply here.

Jean-Paul

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

Showing content from https://mail.python.org/pipermail/python-dev/2010-March/098187.html below:

[Python-Dev] [PEP 3148] futures - execute computations asynchronously