Hi Wolfgang, On 2015-05-05 7:27 AM, Wolfgang wrote: > Hi, [..] > Even the discussion on python-dev suggests there is some time needed > to finalize all this. I'd say that: 80% of the recent discussion of the PEP is about terminology. 10% is about whether we should have __future__ import or not. > > We forget to address the major problems here. How can someone in a > "sync" script use this async stuff easy. How can async and sync stuff > cooperate and we don't need to rewrite the world for async stuff. > How can a normal user access the power of async stuff without rewriting > all his code. So he can use a simple asyc request library in his code. > How can a normal user learn and use all this in an easy way. asyncio and twisted answered these questions ;) The answer is that you have to write async implementations. gevent has a different answer, but greenlents/stackless is something that will never be merged in CPython and other implementations. > > And for all this we still can't tell them "oh the async stuff solves > the multiprocessing problem of Python learn it and switch to version > 3.5". It does not and it is only most useful for networking stuff > nothing more. "networking stuff", and in particular, web, is a huge part of current Python usage. Please don't underestimate that. Thanks, Yury
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4