2014-05-30 0:13 GMT+02:00 Luca Sbardella <[email protected]>: > 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.
The problem is that Trollius is not "fully" compliant with asyncio: http://trollius.readthedocs.org/#differences-between-trollius-and-tulip IMO it's safer to use Trollius even if Python 3.3 to ensure that you have exactly the same behaviour on Python 2 and Python 3. Using "Trollius or asyncio" may be more tricky, the code should be carefully written. > 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. Importing asyncio in Python 2 raises SyntaxError. How do you plan to fix such issue? > 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. How do you write coroutines working on Python 2 and Python 3? > What are the use cases? > None of the big boys are using python 3 yet! I wrote Trollius to help porting code from Python 2 to Python 3. Right now, it opened more questions than it solved :-) Victor
