[Async-sig] Fwd: DEMO-2345 Re: Listening for OS events

o unsubscribe send an email to async-sig-le...@python.org https://mail.python.org/mailman3/lists/async-sig.python.org/ Code of Conduct: https://www.python.org/psf/codeofconduct/ -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com

[Async-sig] Re: correct way to combine two coroutines in a loop

lly "asyncio.wait" was quite hidden in the library (and from > google) and it took me many iterations to understand how to interact > with it properly (although the obvious API is quite simple). > > > ___________ > Async-sig mailing lis

Re: [Async-sig] Inadvertent layering of synchronous code as frameworks adopt asyncio

On Mon, Mar 25, 2019 at 5:11 PM Ben Darnell wrote: > On Mon, Mar 25, 2019 at 8:02 PM Guido van Rossum wrote: > >> >> Given PBP, I wonder if we should just relent and have a configurable flag >> (off by default) to allow nested loop invocations (both the same loop

Re: [Async-sig] Inadvertent layering of synchronous code as frameworks adopt asyncio

On Mon, Mar 25, 2019 at 4:54 PM Ben Darnell wrote: > On Mon, Mar 25, 2019 at 7:37 PM Guido van Rossum wrote: > >> Thanks for bringing this up -- I think it will be good to get to the >> bottom of this, before the Jupyter folks accidentally get everyone to use >> an

Re: [Async-sig] Inadvertent layering of synchronous code as frameworks adopt asyncio

le (for the sake of argument, lets ignore the > possible issues with non-standard event loops) better to my peers. > > Thank you, > > -Dan Nugent > ___ > Async-sig mailing list > Async-sig@python.org > https://mail.python.org/mailman/listinfo/async-sig > Code of

Re: [Async-sig] AI_V4MAPPED on Windows

ync-sig@python.org > https://mail.python.org/mailman/listinfo/async-sig > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) ___ Async-sig mailing list Async-sig@python.org https://mail.python.org/mailman/listinfo/async-sig Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [Async-sig] new library: sniffio – Sniff out which async library your code is running under

Neat! On Thu, Aug 16, 2018 at 9:02 AM Nathaniel Smith wrote: > Hi all, > > A number of people are working on packages that support multiple async > backends (e.g., asyncio + trio, or trio + curio, or trio + twisted, > ...). So then the question arises... how can I figure out which async >

Re: [Async-sig] "Coroutines" sometimes run without being scheduled on an event loop

Depending on the coroutine*not* running sounds like asking for trouble. On Thu, May 3, 2018, 09:38 Andrew Svetlov wrote: > What real problem do you want to solve? > Correct code should always use `await loop.sock_connect(sock, addr)`, it > this case the behavior

Re: [Async-sig] New blog post: Notes on structured concurrency, or: Go statement considered harmful

Adding nurseries to asyncio (or wherever in the stdlib they fit -- if they can be independent from asyncio and shared between asyncio and trio, all the better). On Thu, Apr 26, 2018 at 10:03 PM, Nathaniel Smith <n...@pobox.com> wrote: > On Wed, Apr 25, 2018 at 9:43 PM, Guido van R

Re: [Async-sig] New blog post: Notes on structured concurrency, or: Go statement considered harmful

__ > Async-sig mailing list > Async-sig@python.org > https://mail.python.org/mailman/listinfo/async-sig > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) _

Re: [Async-sig] subclassing CancelledError

I think it's too late to change the cancellation logic. Cancellation is tricky. On Sun, Dec 3, 2017 at 1:53 PM, Chris Jerdonek <chris.jerdo...@gmail.com> wrote: > On Sun, Dec 3, 2017 at 9:04 AM, Guido van Rossum <gu...@python.org> wrote: > > Sounds like an implementation is

Re: [Async-sig] subclassing CancelledError

the narrow "cancelled" channel? On Sun, Dec 3, 2017 at 2:11 AM, Andrew Svetlov <andrew.svet...@gmail.com> wrote: > IIRC at very early stages Guido van Rossum decided to *freeze* > `CancelledError`: user code should not derive from the exception. Like you > never derive from

Re: [Async-sig] awaiting task is not chaining exception

next() on that, it will be pushed on top of whatever is the current stack (i.e. whatever calls next()), which *may* be a completely different stack configuration than when it was suspended. That's all. -- --Guido van Rossum (python.org/~guido) ___ A

Re: [Async-sig] coroutine function vs. function returning awaitable

> advantages (but I haven't tried it): > https://www.python.org/dev/peps/pep-0492/#types-coroutine > > --Chris > > On Thu, Nov 2, 2017 at 8:16 PM, Guido van Rossum <gu...@python.org> wrote: > > iscoroutine() is usually used to turn something into a Future. Is that &g

Re: [Async-sig] coroutine function vs. function returning awaitable

> return value? It looks like asyncio calls that one in a half-dozen places > or so. > > —Chris > > On Thu, Nov 2, 2017 at 7:15 PM Guido van Rossum <gu...@python.org> wrote: > >> Re (1), there are only two places where asyncio calls >> `iscouroutinefunc

Re: [Async-sig] coroutine function vs. function returning awaitable

_aenter__ method). You have to > await to get the underlying async context manager. > > Thanks, > --Chris > ___ > Async-sig mailing list > Async-sig@python.org > https://mail.python.org/mailman/listinfo

Re: [Async-sig] Asyncio-tkinter hope this is the right thread for this

mailman/listinfo/async-sig > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) ___ Async-sig mailing list Async-sig@python.org https://mail.python.org/mailman/listinfo/async-sig Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [Async-sig] using asyncio in synchronous applications

l 9, 2017 at 9:00 PM, Guido van Rossum <gu...@python.org> wrote: > > But the big question is, what is that library doing for you? In the > abstract > > it is hard to give you a good answer. What library is it? What calls are > you > > making? > > It's the web

Re: [Async-sig] async generator confusion or bug?

one's coming from in the end? > > Where did "user-0" and "user-1" data go? > > > > Is this a bug, or am I hopelessly confused? > > Thanks! > > ___ > > Async-sig mailing list > > Async-sig@python.org > > https://mail.python.org/mailman/listinfo/async-sig > > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > ___ > Async-sig mailing list > Async-sig@python.org > https://mail.python.org/mailman/listinfo/async-sig > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) ___ Async-sig mailing list Async-sig@python.org https://mail.python.org/mailman/listinfo/async-sig Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [Async-sig] "read-write" synchronization

ator used in an async task -- but that's just due to the general ban on I/O.) - Using async tasks don't make globals more risky than regular code (in fact they are safer here than in traditional multi-threaded code). - What on earth is "read/write" control from memory space w

Re: [Async-sig] "read-write" synchronization

The secret is that as long as you don't yield no other task will run so you don't need locks at all. On Jun 25, 2017 2:24 PM, "Chris Jerdonek" wrote: > Thank you. I had seen that, but it seems heavier weight than needed. > And it also requires locking on reading. > >

Re: [Async-sig] PyCon US 2017 open space on Saturday sometime after lunch

Sorry I couldn't make it. Stuck in the mypy open space... On May 20, 2017 9:19 AM, "Brett Cannon" wrote: > This is now scheduled for 15:00/3:00pm today. > > On Thu, May 18, 2017, 18:17 Brett Cannon, wrote: > >> I have not picked a time yet and I can't book

Re: [Async-sig] Optional Asynchronous Interface

> Haha clearly too gentle. That’s a shame, I’ll let the high from solving it > fade and reconsider it :) > > Are you able to give me a anything specifically bad with it, or is it more > of a ‘code smell’ kinda thing from your experience? > > > From: Guido van Rossum

Re: [Async-sig] Optional Asynchronous Interface

> Async-sig mailing list > Async-sig@python.org > https://mail.python.org/mailman/listinfo/async-sig > Code of Conduct: https://www.python.org/psf/codeofconduct/ -- --Guido van Rossum (python.org/~guido) ___ Async-sig mailing list Asyn

Re: [Async-sig] SansIO (Was: PEP: asynchronous generators)

d that others have covered before, but…hell, > we can’t all be top-tier programmers! If all I say is that I have repackaged > an idea my intellectual betters have previously made such that it’s more > appealing to the masses, I think I can call myself ha