This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author flox
Recipients flox
Date 2014-02-12.15:13:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I had this sporadic traceback in a project:

  File "", line 62, in <module>
    result = do_lqs(client, str(dnvn))
  File "", line 25, in do_lqs
    qualif_service_id = client.create('ti.qualif.service', {})
  File "/srv/openerp/.buildout/eggs/ERPpeek-1.4.5-py2.6.egg/", line 894, in wrapper
    return self.execute(obj, method, *params, **kwargs)
  File "/srv/openerp/.buildout/eggs/ERPpeek-1.4.5-py2.6.egg/", line 636, in execute
    res = self._execute(obj, method, *params)
  File "/srv/openerp/.buildout/eggs/ERPpeek-1.4.5-py2.6.egg/", line 361, in <lambda>
    wrapper = lambda s, *args: s._dispatch(name, args)
  File "/usr/lib/python2.6/", line 1489, in __request
  File "/usr/lib/python2.6/", line 1235, in request
    self.send_content(h, request_body)
  File "/usr/lib/python2.6/", line 1349, in send_content
  File "/usr/lib/python2.6/", line 908, in endheaders
  File "/usr/lib/python2.6/", line 780, in _send_output
  File "/usr/lib/python2.6/", line 739, in send
  File "/usr/lib/python2.6/", line 1112, in connect
    sock = socket.create_connection((, self.port), self.timeout)
  File "/usr/lib/python2.6/", line 561, in create_connection
    raise error, msg
socket.error: [Errno 4] Interrupted system call

It seems that the EINTR should be caught by the standard library in all cases:

But it's not the case for the "socket.create_connection" method (verified in 3.3 and 2.7 source code).
Date User Action Args
2014-02-12 15:13:52floxsetrecipients: + flox
2014-02-12 15:13:52floxsetmessageid: <>
2014-02-12 15:13:52floxlinkissue20611 messages
2014-02-12 15:13:51floxcreate