On 3 October 2016 at 15:52, Giampaolo Rodola' <g.rod...@gmail.com> wrote: > Independently from what the proposed solution is, I think you raised a very > valid concern: the DRY principle. > Right now the stdlib has tons of client network libraries which do not > support the new async model. > As such, library vendors will have to rewrite them by using the new syntax > and provide an "aftplib", "ahttplib" etc. and release them as third-party > libs hosted on PYPI. This trend is already happening as we speak: > https://github.com/python/asyncio/wiki/ThirdParty#clients > It would be awesome if somehow the Python stdlib itself would provide some > mechanism to make the existent "batteries" able to run asynchronously so > that, say, ftplib or httplib can be used with asyncio as the base IO loop > and at the same time maintain the same existent API. > Gevent tried to do the same thing with > http://www.gevent.org/gevent.monkey.html > As for *how* to do that, I'm sorry to say that I really have no idea. It's a > complicated issue, but I think it's good that this has been raised.
There's https://sans-io.readthedocs.io/ which proposes an approach to solving this issue. Paul _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
