[Python-Dev] [PEP 3148] futures - execute computations asynchronously (original) (raw)
exarkun at twistedmatrix.com exarkun at twistedmatrix.com
Fri Mar 5 19:30:35 CET 2010
- Previous message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Next message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Next message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]