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 | r.david.murray |
|---|---|
| Recipients | amaury.forgeotdarc, ezio.melotti, georg.brandl, r.david.murray |
| Date | 2009年07月13日.02:36:59 |
| SpamBayes Score | 3.721646e-05 |
| Marked as misclassified | No |
| Message-id | <1247452621.75.0.383535447639.issue6471@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Yes, it looks to me like urllib is intentionally putting the 'socket error' or 'url error' into the errno position in the IOError arguments. Now that socket.error is an IOError, that at least seems wrong. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009年07月13日 02:37:01 | r.david.murray | set | recipients: + r.david.murray, georg.brandl, amaury.forgeotdarc, ezio.melotti |
| 2009年07月13日 02:37:01 | r.david.murray | set | messageid: <1247452621.75.0.383535447639.issue6471@psf.upfronthosting.co.za> |
| 2009年07月13日 02:37:00 | r.david.murray | link | issue6471 messages |
| 2009年07月13日 02:37:00 | r.david.murray | create | |