[pypy-issue] Issue #1892: rpyc ThreadedServer vs ForkingServer - different behaviour on pypy3 V2.3.1 and python3.4.1 (pypy/pypy)
bitranox bitranox
issues-reply at bitbucket.org
Thu Oct 16 10:14:31 CEST 2014
New issue 1892: rpyc ThreadedServer vs ForkingServer - different behaviour on pypy3 V2.3.1 and python3.4.1
https://bitbucket.org/pypy/pypy/issue/1892/rpyc-threadedserver-vs-forkingserver
bitranox bitranox:
ThreadedServer vs ForkingServer - different behaviour on pypy3 V2.3.1 and python3.4.1
I use rpyc 3.3 on Linux Mint Mate, either with python3 (Version 3.4.1) or pypy3 (Version 2.3.1)
on python3 - ThreadedServer and ForkingServer working as expected so far.
on pypy3 - ThreadedServer Works, But ForkingServer terminates when a client is closing the connection
rpyc team answer was :
well, it's clearly a pypy bug. i'd suggest you added prints() around the server's code (rpyc/utils/server.py) to see what's going on there. perhaps it's an issue with signals, or what not. donno.
More information about the pypy-issue
mailing list