GLib event loop for tulip (PEP 3156)
As much as possible, except where noted below, it mimics asyncio’s interface. If you notice any differences, please report them.
- python 3.6+
- gtk+3 (optional)
GLib event loop
import asyncio, gbulb gbulb.install() asyncio.get_event_loop().run_forever()
Gtk+ event loop (suitable for GTK+ applications)
import asyncio, gbulb gbulb.install(gtk=True) asyncio.get_event_loop().run_forever()
GApplication/GtkApplication event loop
import asyncio, gbulb gbulb.install(gtk=True) # only necessary if you're using GtkApplication loop = asyncio.get_event_loop() loop.run_forever(application=my_gapplication_object)
Waiting on a signal asynchronously
- Windows is not supported, sorry. If you are interested in this, please help me get it working! I don’t have Windows so I can’t test it.
Divergences with PEP 3156
In GLib, the concept of event loop is split in two classes: GLib.MainContext and GLib.MainLoop.
The event loop is mostly implemented by MainContext. MainLoop is just a wrapper that implements the run() and quit() functions. MainLoop.run() atomically acquires a MainContext and repeatedly calls MainContext.iteration() until MainLoop.quit() is called.
A MainContext is not bound to a particular thread, however it cannot be used by multiple threads concurrently. If the context is owned by another thread, then MainLoop.run() will block until the context is released by the other thread.
MainLoop.run() may be called recursively by the same thread (this is mainly used for implementing modal dialogs in Gtk).
The issue: given a context, GLib provides no ways to know if there is an existing event loop running for that context. It implies the following divergences with PEP 3156:
- .run_forever() and .run_until_complete() are not guaranteed to run immediately. If the context is owned by another thread, then they will block until the context is released by the other thread.
- .stop() is relevant only when the currently running Glib.MainLoop object
was created by this asyncio object (i.e. by calling .run_forever() or
.run_until_complete()). The event loop will quit only when it regains
control of the context. This can happen in two cases:
- when multiple event loop are enclosed (by creating new MainLoop objects and calling .run() recursively)
- when the event loop has not even yet started because it is still trying to acquire the context
It would be wiser not to use any recursion at all. GLibEventLoop will actually prevent you from doing that (in accordance with PEP 3156), however GtkEventLoop will allow you to call run() recursively. You should also keep in mind that enclosed loops may be started at any time by third-party code calling GLib’s primitives.
gblub is part of the BeeWare suite. You can talk to the community through:
We foster a welcoming and respectful community as described in our BeeWare Community Code of Conduct.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size gbulb-0.6.2-py2.py3-none-any.whl (17.3 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View|
|Filename, size gbulb-0.6.2.tar.gz (27.2 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for gbulb-0.6.2-py2.py3-none-any.whl