[Python-Dev] Does anyone care enough about asyncore and asynchat to help adapt their APIs for Py3k?

[Guido van Rossum]

On Dec 5, 2007 6:34 PM, Daniel Arbuckle <djarb at highenergymagic.org> wrote:
> Guido van Rossum wrote:
> > The asyncore and asynchat modules are in a difficult position when it
> > comes to Python 3000. None of the core developers use it or
> > particularly care about it (AFAIK), and the API has problems because
> > it wasn't written to deal with bytes vs. unicode. E.g. in
> > http://bugs.python.org/issue1067, Thomas suggests that these modules
> > need to be rewritten to use bytes internally and have separate APIs to
> > handle (unicode) text as desired, similar to the way file I/O was
> > redesigned. Another alternative would be to make these modules deal
> > strictly in bytes, but that would probably vastly reduce their
> > usefulness (though I don't know -- as I said, I don't use them).
>
> I guess that would be me, if you'll have me. I think asyncore and
> asynchat are valuable, and I'm willing to do what needs to be done to
> ensure that they remain in Py3k.

Excellent!

Are you at all familiar with how Py3k deals with bytes vs strings? If
not, perhaps you could start by reading PEP 3137. I'd be happy to
answer any questions you have (possibly off-list).

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)