It looks like the code is currently moving fast. I suggest to wait until Python 3.6 to stabilize the Python C API for async/await. It's a pain to maintain a public API. I hate having to add 2 or 3 versions of a single function :-(
Victor 2015-06-25 17:43 GMT+02:00 Yury Selivanov <yselivanov...@gmail.com>: > Hi Arc, > > > On 2015-06-24 10:36 PM, Arc Riley wrote: >> >> A type slot for tp_as_async has already been added (which is good!) but we >> do not currently seem to have protocol functions for awaitable types. >> >> I would expect to find an Awaitable Protocol listed under Abstract Objects >> Layer, with functions like PyAwait_Check, PyAwaitIter_Check, and >> PyAwaitIter_Next, etc. >> >> Specifically its currently difficult to test whether an object is >> awaitable >> or an awaitable iterable, or use said objects from the c-api without >> relying on method testing/calling mechanisms. > > > The request is reasonable, I created a couple of bug tracker > issues: > > http://bugs.python.org/issue24511 > http://bugs.python.org/issue24510 > > Let's continue the discussion there. > > Yury > > _______________________________________________ > 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/victor.stinner%40gmail.com _______________________________________________ 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
