asyncio-glib

asyncio-glib copied to clipboard

Also listen for HUP signal

1

Fix for issue #5

nielsavonds

glib_selector: Only ever iterate the mainloop once

1

As it is right now, any python code that runs may modify the timeout that would be passed into the select() call. As such, we can only run a single...

benzea

Wrote some tests to better describe and indicate current issues (not all fail). These new tests run twice, once to verify the behavior of the test itself (asyncio with default...

ReadWriteDenied

Wag the dog – i.e. enslave the python mainloop to the GMainContext

1

benzea

GTK example

8

Could you include an example of how you would use this with a GTK application? For example, convert the below program into asyncio, while replacing the time.sleep() with an await...

Dreamsorcerer

Potential fix for issue #3

1

This change fixes my issue in #3. I haven't done any testing to see if a broader fix might be needed (e.g., do call_later() calls suffer from the same issue...

talljosh

Restart loop on demand

1

This will quit the GLib main loop in two events: * A new task is created * A Future finishes See #1 for discussion on motivation for this. I think...

chrysn

When running a subprocess using asyncio-glib and having stdout as a PIPE, the EOF is never received. This happens because the selector doesn't listen for the GLib HUP signal. A...

nielsavonds

Callback is never called when set_result() is called on a Future

3

When code triggered by a Gtk signal calls `set_result()` on an asyncio Future object, it seems the callbacks on the Future object are not called unless something else wakes up...

talljosh