<br><br><div class="gmail_quote">On Sun, Jun 3, 2012 at 4:24 PM, Fernando Perez <span dir="ltr"><<a href="mailto:fperez.net@gmail.com" target="_blank">fperez.net@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Sun, Jun 3, 2012 at 4:02 PM, MinRK <<a href="mailto:benjaminrk@gmail.com">benjaminrk@gmail.com</a>> wrote:<br>
> But instead of waiting for all of the results and then iterating through<br>
> them, the results are awaited one by one as the iteration requires.<br>
<br>
</div>Quick question: the wait is still done in the order they are in<br>
mapresult, right? So if by chance the first element takes say 10<br>
minutes but all the others finish in one, the others still have to<br>
wait for the first to be processed? Or does the iterator advance as<br>
results arrive in arbitrary order? I seem to remember there was an<br>
option for that...<br></blockquote><div><br></div><div>That's what Jon mentioned above as the `ordered=True|False` flag. By default, ordering is preserved, but you can disable that and process first-come-first-serve if you don't care about the order.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
<div class="HOEnZb"><div class="h5"><br>
f<br>
_______________________________________________<br>
IPython-User mailing list<br>
<a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
</div></div></blockquote></div><br>