On 23 November 2017 at 09:14, Steve Holden <st...@holdenweb.com> wrote: > I would urge developers, in their improvements to the language to support > asynchronous programming, to bear in mind that this is (currently) a > minority use case. Why the rush to set complex semantics in stone?
+1 Also, given that languages like C# have similar async/await functionality, I'd be interested to know how they address questions like this. If they have a parallel, we should probably follow it. If they don't that would be further indication that no-one has much experience of the "best answers" yet, and caution is indicated. BTW, I'm assuming that the end goal is for async to be a natural and fully-integrated part of the language, no more "minority use" than generators, or context managers. Assuming that's the case, I think that keeping a very careful eye on how intuitive async feels to non-specialists is crucial (so thanks to Ivan and Yury for taking the time to respond to this discussion). Paul _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
