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 | giampaolo.rodola, maker, r.david.murray, terry.reedy, vinay.sajip |
| Date | 2012年05月15日.01:17:49 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1337044673.9.0.169435539664.issue11959@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm finally getting back around to this. If asyncore and asynchat are (mostly?) supporting an alternate socket map, why is it necessary to copy create_socket? Shouldn't we be fixing create_socket in asyncore instead? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年05月15日 01:17:54 | r.david.murray | set | recipients: + r.david.murray, terry.reedy, vinay.sajip, giampaolo.rodola, maker |
| 2012年05月15日 01:17:53 | r.david.murray | set | messageid: <1337044673.9.0.169435539664.issue11959@psf.upfronthosting.co.za> |
| 2012年05月15日 01:17:50 | r.david.murray | link | issue11959 messages |
| 2012年05月15日 01:17:49 | r.david.murray | create | |