Jason Madden

> Central to it is `gevent.getcurrent`, which is used to determine if the execution context has changed. Did 1.3b1 introduce a change there? No, `gevent.getcurrent` is just an alias for...

Ah, and if I go to https://github.com/nedbat/coveragepy/issues/841 I see that `PURE_PYTHON` indeed fixes it. I confirmed locally that 1.5a2 doesn't make a difference.

Making a small modification to the example program and running it with a plain `python -m trace` does show the lines as executed, though `coverage --concurrency=gevent` still misses them (as...

I tweaked `gevent.getcurrent` to report what Python thinks the traceback is when its called, and what greenlet it returns (just added some print statements and a wrapper around `greenlet.getcurrent`) so...

I'm not sure we can change the semantics of `map` for backwards compatibility. But you can write your own loop to do what you want using `pool.start`: ```python try: for...

Only very simple uses of `multiprocessing.Process` are supported in a monkey-patched environment; the higher level abstractions are not. This is poorly documented (there's just a note on `gevent.monkey.patch_thread`), so that...

The previous comment is correct, gevent 20.9 doesn't support re-cythonizing with that new of a version of Cython. You need to use a newer version of gevent or an older...

If people have written the code, than apparently it is possible. But if there are existing projects that do this, I don't see a need for gevent to copy them...

That's coming from here: https://github.com/gevent/gevent/blob/69f361369400cdc77053a70f3b86c6fa7bf341b3/src/gevent/_abstract_linkable.py#L205-L210 It means that you're trying to use a `gevent.event.Event` from more than one real/native Thread. That's illegal; all gevent objects can only be used by...

I don't know anything about dash or the other libraries you're using, but you since you cannot use an `Event` from two different threads, you basically have two options: 1)...