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. |
|