> I started working on a PEP last year, but I didn't get very far partly > because I doubted the desire. > > What part do you think is a hard problem? Convincing people to switch to a > new API? *Defining* the new API doesn't seem very hard to me. >
I must say that the only time I needed the functionality asyncore provides in some Python code, 5 minutes of browsing and reading pointed me to Twisted anyway. I think that having the "ultimately recommended" library for such programming in stdlib is a good idea, or at least some core of it. We have a tradition of new modules replacing old ones with the same functionality gradually (command line argument parsing, for example) and if someone is motivated enough to prepare a comprehensive PEP and then working on pulling it through, I think it may work. Eli _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
