Hi Victor,
On 20 May 2014 14:55, Victor Stinner <[email protected]> wrote: > Hi, > > I synchronized Trollius with Tulip 3.4.1. As discussed on this list, I > also chose to rename "asyncio" to "trollius" to make it possible to > use Trollius on Python 3.4+. > > It is now more explicit than Trollius and Tulip are two different > projects which are "almost the same" but are different (yield from ... > vs yield From(...)). > > bit late on this rather bizarre change, my fault. > It's still a beta version. I plan to release a new version this week. > I hesitate between the version "0.3" and the version "1.0". > > It would be nice if someone can test the folllowing projects which are > known to work on Tulip and Trollius: > > - AutobahnPython > - Pulsar > - Tornado > - aiodns > > You will need to modify the source code to add the following code at > the top of files using asyncio: > --- > try: > # Use Trollius on Python <= 3.2 > import trollius as asyncio > except ImportError: > # Use Tulip on Python 3.3, or builtin asyncio on Python 3.4+ > import asyncio > --- > I've changed pulsar accordingly, fortunately it was a trivial task since pulsar import asyncio via pulsar itself from pulsar import asyncio I only needed to change one file, result! Warning, Rant Alert! But, I must say, I don't get why you did it. In my opinion trollius should go up to python 3.2 and then stop. Do we need two asyncio implementations after that? I don't really think so. Asynchronous concepts are hard enough that adding the py 2 & 3 mess is just too much. If library authors want to support asyncio on py 2 & 3, they should do so on their terms, and it is not too difficult. Pulsar does it by *simply* overriding the _step method in the Task class. What are the use cases? None of the big boys are using python 3 yet! -- http://lucasbardella.com
