- Corrected the import of
InvalidStateError
to fix an error seen on Python 3.8+. (#56) - Reverted the fix from #47; that change led to file descriptor leaks. (#52)
- Added support for Python 3.10. (#50)
- Corrects a problem where a socket isn't forgotten and causes 100% CPU load. (#47)
- (#49)
- Support for 3.7, for real this time. Thank you Philippe Normand!
- Support for 3.7.
- Preliminary Windows support. Please note that using subprocesses is known not to work. Patches welcome.
- Support for 3.4 and below has been dropped.
- Implemented child watcher setters and getters to allow writing tests with
- asynctest for code using gbulb.
gbulb.install
now monkey patchesasyncio.SafeChildWatcher
togbulb.glib_events.GLibChildWatcher
, to ensure that any library code that uses it will use the correct child watcher.
- Fixed a sporadic test hang.
- Fixed breakage on Python versions older than 3.5.3, caused by 0.5.0. Thanks Brecht De Vlieger!
- Fixed issue with readers and writers not being added to the loop properly as a result of Python Issue 28369.
- gbulb will no longer allow you to schedule coroutines with
call_at
,call_soon
andcall_later
, the same as asyncio.
- gbulb will no longer occasionally leak memory when used with threads.
gbulb.install
to simplify installation of a GLib-based event loop in- asyncio:
- Connecting sockets now works as intended
- Implement
call_soon_threadsafe
- Lots of tests
- API BREAKAGE No implicit Gtk import anymore.
GtkEventLoop
andGtkEventLoopPolicy
have been moved togbulb.gtk
- API BREAKAGE No more
threads
,default
orfull
parameters for event loop policy objects. gbulb now does nothing with threads. - API BREAKAGE
gbulb.get_default_loop
has been removed - Permit running event loops recursively via
.run()
- Default signal handling of SIGINT
gbulb.wait_signal.cancel()
now obeys the interface defined byasyncio.Future
- Initial release