James Yonan openvpn.net> writes:
>
> I'd like to propose that the Python community standardize on a
> "deferred" object for asynchronous return values, modeled after the
> well-thought-out Twisted Deferred class.
Ummm, sorry, I seem to need new glasses :-( ignore my last post.
James Yonan openvpn.net> writes:
> I'd like to propose that the Python community standardize on a
> "deferred" object for asynchronous return values
Have a look at PEP 3148:
http://www.python.org/dev/peps/pep-3148/
___
Python-Dev mailing list
Pyth
Moving to python-ideas.
Have you seen http://www.python.org/dev/peps/pep-3148/ ? That seems
exactly what you want.
--Guido
On Fri, Sep 10, 2010 at 4:00 PM, James Yonan wrote:
> I'd like to propose that the Python community standardize on a "deferred"
> object for asynchronous return values, mod
I'd like to propose that the Python community standardize on a
"deferred" object for asynchronous return values, modeled after the
well-thought-out Twisted Deferred class.
With more and more Python libraries implementing asynchronicity (for
example Futures -- PEP 3148), it's crucial to have a
