On Mon, Jul 12, 2010 at 02:13, Jesse Noller wrote:
> On Sat, May 22, 2010 at 11:38 AM, Guido van Rossum
> wrote:
> [snip]
> > Great points Jesse! Since I really don't have the time or expertise to
> > make a judgment on this PEP, I hereby appoint you chair of the
> > approval process for this PE
Titus von der Malsburg wrote:
None of the examples I found used the pythonic
exception style, that's why I assumed that checking the "return value"
is the only possibility. Reading the PEP carefully would have helped.
:-)
I had to read the pep fairly carefully before I noticed
this too, so per
On 13 Jul 2010, at 00:59, Titus von der Malsburg wrote:
On Tue, Jul 13, 2010 at 12:48:35AM +1000, Nick Coghlan wrote:
On Tue, Jul 13, 2010 at 12:19 AM, Titus von der Malsburg
That's what actually happens, so you can code it either way
That's great! None of the examples I found used the pyth
On Tue, Jul 13, 2010 at 12:48:35AM +1000, Nick Coghlan wrote:
> On Tue, Jul 13, 2010 at 12:19 AM, Titus von der Malsburg
> That's what actually happens, so you can code it either way
That's great! None of the examples I found used the pythonic
exception style, that's why I assumed that checking t
On Tue, Jul 13, 2010 at 12:19 AM, Titus von der Malsburg
wrote:
> This reminds me a lot of how things are done in C but it's not very
> pythonic. Wouldn't it be possible and nicer to raise the exception --
> if there was one inside the asynchronous job -- when the result of the
> future is access
Hi I learned about the futures PEP only today. I saw the example on
http://code.google.com/p/pythonfutures/
One thing that worries me is that this approach seems to bypass the
usual exception handling mechanism of Python. In particular I'm
wondering why you have to do things like:
if future.e
2010/7/11 Jesse Noller :
> On Sun, Jul 11, 2010 at 10:07 PM, Benjamin Peterson
> wrote:
>> 2010/7/11 Jesse Noller :
>>> On Sat, May 22, 2010 at 11:38 AM, Guido van Rossum wrote:
>>> [snip]
Great points Jesse! Since I really don't have the time or expertise to
make a judgment on this PE
On Sun, Jul 11, 2010 at 10:07 PM, Benjamin Peterson wrote:
> 2010/7/11 Jesse Noller :
>> On Sat, May 22, 2010 at 11:38 AM, Guido van Rossum wrote:
>> [snip]
>>> Great points Jesse! Since I really don't have the time or expertise to
>>> make a judgment on this PEP, I hereby appoint you chair of th
2010/7/11 Jesse Noller :
> On Sat, May 22, 2010 at 11:38 AM, Guido van Rossum wrote:
> [snip]
>> Great points Jesse! Since I really don't have the time or expertise to
>> make a judgment on this PEP, I hereby appoint you chair of the
>> approval process for this PEP. That basically means that when
On Sat, May 22, 2010 at 11:38 AM, Guido van Rossum wrote:
[snip]
> Great points Jesse! Since I really don't have the time or expertise to
> make a judgment on this PEP, I hereby appoint you chair of the
> approval process for this PEP. That basically means that when you
> think it's ready to be ap
10 matches
Mail list logo
