Message250214
| Author | r.david.murray |
|---|---|
| Recipients | barry, brett.cannon, dstufft, eric.smith, gvanrossum, r.david.murray, rhettinger, vstinner |
| Date | 2015-09-08.15:20:17 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1441725618.24.0.6246322929.issue25002@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Yes, stopping changing asyncore/asynchat also means it becomes a stable target for people who *are* using it for 2/3 code. We may have effectively done this already (without closing the open issues): the last asyncore-specific change (as opposed to library-wide changes that also hit asyncore) was a ResourceWarning added by Victor in June of 2014. Likewise for asynchat. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-09-08 15:20:18 | r.david.murray | set | recipients: + r.david.murray, gvanrossum, barry, brett.cannon, rhettinger, vstinner, eric.smith, dstufft |
| 2015-09-08 15:20:18 | r.david.murray | set | messageid: <1441725618.24.0.6246322929.issue25002@psf.upfronthosting.co.za> |
| 2015-09-08 15:20:18 | r.david.murray | link | issue25002 messages |
| 2015-09-08 15:20:17 | r.david.murray | create | |