[Python-Dev] asyncore fixes in Python 2.6 broke Zope's version of medusa
Tres Seaver
tseaver at palladion.com
Tue Mar 3 23:13:06 CET 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Guido van Rossum wrote:
> On Tue, Mar 3, 2009 at 12:23 PM, Tres Seaver <tseaver at palladion.com> wrote:
>> How is anybody supposed to
>> write a package which sits atop a library like asyncore in a fashion
>> portable across Python versions? The changes to the implementation in
>> 2.6 (there is no real API) can't be reconciled, AFAICT.
>
> This seems to be the crux of the problem with asyncore, ever since it
> was added to the stdlib -- there's no real API, so every change
> potentially breaks something. I wish we could start over with a proper
> design under a new name. Maybe packages requiring asyncore
> functionality should just copy the version of asyncore they like into
> their own three and stick with that.
That was the very solution Chris came up with earlier today: "stick a
fork in it, its done!"
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJraty+gerLs4ltQ4RAjBSAJ4niecZJusKY4XiioJ18mdhdMixxQCfWvcQ
Dwkh1ZBuxtGRbhUI4qy96Sc=
=ms0I
-----END PGP SIGNATURE-----
More information about the Python-Dev
mailing list