10.03.2011 08:31, Antoine Dechaume kirjoitti:
Have a look at this:
http://code.google.com/p/pythonfutures
I recently backported the code from Python 3.2 stdlib to Python 2.5-2.7
and 3.1. It does not work on Python 2.4 however because I did not dare
touch the various "with" statements littered all over the code. The
backport is available on PyPI here:
http://pypi.python.org/pypi/futures/2.1.2
Antoine.
On Thu, Mar 10, 2011 at 6:38 AM, Fruch <[email protected]
<mailto:[email protected]>> wrote:
here is the code:
https://gist.github.com/863616
(you'll need to start a rpyc server and pushy server on localhost
in the background,
mine was embedded inside a C program, so I didn't attached it)
from my POV, pushy is actually achieving all the three goals
you've mentioned.
and as he said on his blog, RPyC was his inspiration.
he sure did a good job. I still think we should
reconsider merging with his code.
adding a wrapper to support the old rpyc code
BTW, I've found this:
http://stackoverflow.com/questions/1239035/asynchronous-method-call-in-python
it has in one of the replays nice replacement for async, that
should work with client code only (I've haven't tried it yet with
pushy/rpyc)
