Pascal Chambon chambon.pas...@gmail.com added the comment:
Allright, it actually looks more like a pathological latency behaviour of my
target platforms than a ssl bug...
I was mislead by the heavy history of socket.settimeout(), sorry. _
--
status: open - closed
Changes by R. David Murray rdmur...@bitdance.com:
--
resolution: - invalid
stage: - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10327
___
New submission from Pascal Chambon chambon.pas...@gmail.com:
On freebsd 8, using python 2.6.6, I've run into the bug already widely dealt
with in these reports :
http://bugs.python.org/issue1380952
http://bugs.python.org/issue1153016
When using socket timeouts (eg. with
Malte Helmert helm...@informatik.uni-freiburg.de added the comment:
I checked if issue1153016 has reappeared for me (Ubuntu, Python 2.6.6), but it
hasn't. Both the urllib and the imaplib examples given there work fine for me.
Or at least opening the connections works fine for me, which it
Antoine Pitrou pit...@free.fr added the comment:
When using socket timeouts (eg. with socket.setdefaulttimeout()),
whatever the timeout I use (eg. 10 seconds), I begin having random
SSLError: The read operation timed out exceptions in my http calls,
via urlopen or 3rd party libraries.
Well,
Pascal Chambon chambon.pas...@gmail.com added the comment:
The exception is raised too early, none of my calls takes more than 1-2 seconds
and I've a default timeout set at 10s or more.
This occurs rather rarely, one or two times on some hundreds of calls. I'll
make a little script to try to
Pascal Chambon chambon.pas...@gmail.com added the comment:
Humz on second thought you may be right, now I have some trouble reproducing
the bugs (wich have been there since the beginning, though), so it may be that
the webservice I call seldom takes 10+ seconds to answer (weird anyway).
I've
