[Python-Dev] asyncore 2.1.1/2.2 incompatibility (original) (raw)

Taral taral@taral.net
Sat, 23 Mar 2002 11:15:18 -0600

--mojUlQ0s9EVzWg2t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

On Sat, Mar 23, 2002 at 06:09:27AM -0800, Zooko wrote:

BTW, I intend to try an alternative to asyncore.py, written by taral@taral.net if I have time to experiment with it. This alternative uses an interface in which the higher-level code registers and unregisters, instead of the asyncore interface in which the lower level code polls the higher level asking "Now are you ready? Now are you ready?". This change will hopefully eliminate the last performance hotspot in my comms code as identified by profiling.

Note that the current "correct" way to cause a program to exit from async.run() is to throw an exception that you catch outside, e.g.:

try: async.run() except MyException: pass

=2E..

def some_async_handler(...): blah, blah if something: throw MyException() and so on.

--=20 Taral <taral@taral.net> This message is digitally signed. Please PGP encrypt mail to me. "Pretty please with dollars on top?" -- Me

--mojUlQ0s9EVzWg2t Content-Type: application/pgp-signature Content-Disposition: inline

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjycuCUACgkQoQQF8xCPwJQy8wCeNFYKdoT+kgH607Q642BGx8sj atEAn0eOBwhAD5fp1jfcmb0CeVZesM5Y =EKLx -----END PGP SIGNATURE-----

--mojUlQ0s9EVzWg2t--