Message90462
No, it seems that 2.5 has the same problem. The 'socket error' message is
raised in urllib.py. The socket module is innocent to me...
It appears that this file routinely raises IOErrors, passing various
arguments, which are not stored properly in the IOError object. IMO it
should raise subclasses of IOError.
In this particular case of "socket error", it should let the exception
propagate. Other occurrences need more thinking. |
|
Date |
User |
Action |
Args |
2009-07-12 23:15:18 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, georg.brandl, ezio.melotti |
2009-07-12 23:15:18 | amaury.forgeotdarc | set | messageid: <1247440518.36.0.827257466408.issue6471@psf.upfronthosting.co.za> |
2009-07-12 23:15:16 | amaury.forgeotdarc | link | issue6471 messages |
2009-07-12 23:15:16 | amaury.forgeotdarc | create | |
|