On Wed, Oct 5, 2016 at 3:40 AM, Sven R. Kunze <srku...@mail.de> wrote: > I don't think that's actually what I wanted here. One simple keyword should > have sufficed just like golang did. So, the developer gets a way to decide > whether or not he needs it blocking or nonblocking **when using a > function**. He doesn't need to decide it **when writing the function**.
The only way to do that is to write *every* function as async, and then if you want it blocking, you immediately wait for it. In other words, you write everything asynchronously. ChrisA _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
