-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mar 4, 2009, at 2:44 PM, gl...@divmod.com wrote:
Maintaining compatibility with the 2.6.x version of asyncore
presupposes that *someone* has written some software against that
version of asyncore and it might break if they installed an upgrade,
though. If that's the case - if there's even one person who has
written or run any asyncore software against the version in 2.6 -
then I think maintaining bug-for-bug compatibility is important.
However, my guess - and I'm assuming that JP was thinking the same
thing - is that literally nobody has done that, or even *would* ever
do that, so there's no software anywhere in the world that would
break. asyncore is relatively unpopular (thanks in part to the
excellent alternatives :-)); its major users are the same people who
have already complained.
FWIW, I use smtpd.py and a few of the asyncore APIs
(.loop(), .socket_map.clear(), and .close_all()) in the Mailman 3 test
suite. That only works on Python 2.6 and I don't recall even a hiccup
when moving from 2.5 to 2.6.
Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSa7kiXEjvBPtnXfVAQI2BQP/XD71ipSv5OhtdOJt+OF2jbfOyFU/2vPR
iJ33g9JJ2A0CvDWXmc81t9hMH3U8waagkXaDUF4r2MNM3JbONSjQGGZqX6X/1UOB
XCT+jNOrbRw2VQR0qjrweQ5A8u0Y1zsDo/rD4CXe0K1pFFWLubaU3lVgqEBMBL8r
xvf77EMoUuA=
=vmM5
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
