Jelte Fennema added the comment:
Is there any issue in merging this? TCP_USER_TIMEOUT is quite useful, for
automatic failover of connections that suddenly died.
--
nosy: +JelteF
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Jelte Fennema added the comment:
No problem, I'm glad to have contributed something to the language I use the
most.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Jelte Fennema added the comment:
I don't know much about the server as I only used the client. So I don't know
if it is possible to test with Python's XML-RPC server.
As for your proposed improvement, it seems that should work. Keep in mind
though that that would also catch
Jelte Fennema added the comment:
>From what I can see that change simply replaces the old BadStatusLine
>exception with the new RemoteDisconnected one. But since BadStatusLine is not
>a subclass of OSError the correct code path would be taken. Currently the path
>in execpt Remote
Changes by Jelte Fennema <pythonbugs-t...@jeltef.nl>:
--
title: Regression in Python 3.5 http.client, raises RemoteDisconnected
seemingly randomly. -> Regression in Python 3.5 xmlrpc.client, raises
RemoteDisconnected seemingly randomly.
_
Jelte Fennema added the comment:
A short look through the stacktrace actually seemed to have gotten me to the
issue. It is in the xmlrpc.client library in this piece of code:
for i in (0, 1):
try:
return self.single_request(host, handler, request_body
New submission from Jelte Fennema:
I've been developing an application which uses fuse as in interface to an
xmlrpc API. I developed it with python 3.4 and it worked fine. When I used
python 3.5 it started randomly raising a specific error when requesting info
using the xmlrpc API.
The error
Changes by Jelte pyt...@tjeb.nl:
--
nosy: +Tjebbe
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11147
___
___
Python-bugs-list mailing list
