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 | pakal |
|---|---|
| Recipients | arekm, georg.brandl, maltehelmert, pakal, pitrou, pristine777, tarek-ziade, twouters |
| Date | 2010年11月08日.11:53:45 |
| SpamBayes Score | 1.6870834e-05 |
| Marked as misclassified | No |
| Message-id | <1289217231.25.0.21509444521.issue10327@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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. >_< |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010年11月08日 11:53:51 | pakal | set | recipients: + pakal, twouters, georg.brandl, pristine777, arekm, maltehelmert, pitrou, tarek-ziade |
| 2010年11月08日 11:53:51 | pakal | set | messageid: <1289217231.25.0.21509444521.issue10327@psf.upfronthosting.co.za> |
| 2010年11月08日 11:53:45 | pakal | link | issue10327 messages |
| 2010年11月08日 11:53:45 | pakal | create | |