Message85233
| Author | tseaver |
|---|---|
| Recipients | akuchling, djarb, facundobatista, forest, giampaolo.rodola, gvanrossum, intgr, j1m, jafo, josiahcarlson, kevinwatters, markb, mcdonc, stutzbach, tseaver |
| Date | 2009-04-02.18:24:53 |
| SpamBayes Score | 0.0012648576 |
| Marked as misclassified | No |
| Message-id | <49D502EB.20405@agendaless.com> |
| In-reply-to | <ca471dc20904021026h45da4ea3hb9f9b63f9afbfe19@mail.gmail.com> |
| Content | |
|---|---|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guido van Rossum wrote: > ISTR that Zope has or had significant monkeypatches to at least one of > asyncore/asynchat. The resulting coupling between Zope and asyn* has > meant that the de-facto API of asyn* was much more than the documented > API. IMO that's a sign of a poorly designed API (in asyn*). If Zope > had had its own copy of asyn* (under a different name of course) that > relied only on lower-level APIs (sockets and select), it could have > evolved that copy directly without the need for monkeypatching. Zope does not monkeypatch asyncore or asynchat, and hasn't since at least Zope 2.5 (the oldest checkout I have, first released 2002-01-25). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@agendaless.com Agendaless Consulting http://agendaless.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ1QLqFXKVXuSL+CMRAhelAJ9yYgo1RXUhWR2cH8CjYRoXz/qsvACgg13O BFAiRoYP8AWVgQVWBhVhB+4= =wj2y -----END PGP SIGNATURE----- |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-04-02 18:24:56 | tseaver | set | recipients: + tseaver, gvanrossum, akuchling, facundobatista, jafo, josiahcarlson, forest, giampaolo.rodola, kevinwatters, djarb, stutzbach, markb, intgr, mcdonc, j1m |
| 2009-04-02 18:24:54 | tseaver | link | issue1641 messages |
| 2009-04-02 18:24:54 | tseaver | create | |