Comments on: PEP 3148 Accepted: “futures — execute computations asynchronously”

By: jnoller

jnoller — Fri, 23 Jul 2010 01:40:12 +0000

You can make custom subclasses as needed. The core libraries do not need to account for 3rd party libraries.

By: gdamjan

gdamjan — Thu, 22 Jul 2010 05:07:58 +0000

(not following the original discussions)
I hope the new concurent package would also be usefull with gevent/greenlets too

By: jnoller

jnoller — Mon, 12 Jul 2010 20:33:25 +0000

By: tmalsburg

tmalsburg — Mon, 12 Jul 2010 19:03:38 +0000

Why “if future.exception() is not None”? (I’m referring to this example:http://code.google.com/p/pythonfutures/ ) Is Python becoming the next C? Could the exception not be thrown when the result is accessed, i.e. on future.result().
I find it really ugly that this proposal bypasses Python’s exception handling and comes up with a new mechanism.

By: Baczek

Baczek — Mon, 12 Jul 2010 18:11:44 +0000

glad to hear that.

By: jnoller

jnoller — Mon, 12 Jul 2010 17:46:30 +0000

The twisted folk provided feedback

By: Baczek

Baczek — Mon, 12 Jul 2010 17:33:07 +0000

i hope this was done with at least some cooperation with twisted guys…

By: jnoller

jnoller — Mon, 12 Jul 2010 16:20:21 +0000

Yay!

By: jnoller

jnoller — Mon, 12 Jul 2010 16:20:14 +0000

Those are class names, and classes in python are typically camel case.

By: Nick Coghlan

Nick Coghlan — Mon, 12 Jul 2010 12:24:00 +0000

I recommend that talk — it did a nice job of showing how easy the PEP makes it to take an iterative algorithm using map and turn it into a parallel algorithm using futures.