-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
?
This is an old problem. Once I tried to deal with that
but could
not
Yes it is this problem, thanks for mentioning it!!
reproduce the error on purpose. How to create a test
environment
for such network errors?
Exactly THAT is the point!! ;) Since the output of the exception does
not work it is close to impossible to reproduce this. I was thinking
about a clean way of forcing the error... but as mentioned in the very
first mail "I think it is related to network timeouts" - may be just
pulling the plug while waiting for answer on a network request would
do that job... but as you see it is no nice 'reproduction'... ;))
Would the mentioned code 'output(u"%r"% e)' print the object for sure?
Is it known to avoid those errors or was it just an assumption? If it
is known (for sure) to help then I would suggest to change to:
output(u"%r"% e)
output(u"%s" % e)
in order to get hints about the issue in the future.
Greetings
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAk/oN2sACgkQAXWvBxzBrDCs3wCeMUtxNUwHOZjoqm6wKzqrplMf
EaYAnj3eKkrM/O+7wYs/E5A16iNeJYVs
=DDFG
-----END PGP SIGNATURE-----