ib_async not working with Python 3.14

[gamubati]

I cannot run ib_async with Python 3.14 (I was getting the same error with ib_insync with Python 3.14 while it was running with Python 3.13). I get the following RunTimeError:

$ python
Python 3.14.2 (main, Jan 2 2026, 14:27:39) [GCC 15.2.1 20251112] on linux
Type "help", "copyright", "credits" or "license" for more information.

from ib_async import *
Traceback (most recent call last):
File "", line 1, in
from ib_async import *
File "/Jts/python/ib_async/init.py", line 6, in
from eventkit import Event
File "/Jts/python/eventkit/init.py", line 3, in
from .event import Event
File "/Jts/python/eventkit/event.py", line 9, in
from .util import NO_VALUE, get_event_loop, main_event_loop
File "/Jts/python/eventkit/util.py", line 24, in
main_event_loop = get_event_loop()
File "/Jts/python/eventkit/util.py", line 21, in get_event_loop
return asyncio.get_event_loop_policy().get_event_loop()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/lib/python3.14/asyncio/events.py", line 715, in get_event_loop
raise RuntimeError('There is no current event loop in thread %r.'
% threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'MainThread'.

[gnzsnz]

please check #200, there is a work around available.

[mattsta]

ah indeed, sorry, we'll add the fix officially soon. also everybody should just be more aware about how doing anything async in ipython or the cli itself is usually weird/bad in its own way.

one of the downsides of python is it makes ipython/notebooks/python-cli look so inviting, but it's not 100% "python-runtime-compatible" then everything ends up more unstable and fragile than just writing actual well-structured reusable test/exploratory scripts in the first place.

[gamubati]

This seems to be a different issue though.

While the previous error appeared in "/usr/lib/python3.14/asyncio/timeouts.py", line 88, in aenter (ultra1971/backtrader_ib_insync#10 (comment)) this error appears in "/usr/lib/python3.14/asyncio/events.py", line 715, in get_event_loop.

[gnzsnz]

This is working fine on #200 because the event loop is already running.

On py314 get_event_loop will raise an exception.

https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.get_event_loop

Changed in version 3.14: Raises a RuntimeError if there is no current event loop.

@mattsta PR #9 submited to eventkit should deal with this case. However i'm having second thoughts on the changes that it introduces to Event.run it's cancelling pending tasks, which i added to "fix" the errors that it throws while running tests, but is bad if there is anything else running in the event loop, like let's say ib_async. in short the fix that you pushed for ib_async in 049e86f should be applied in eventkit.

[mpolavieja]

I confirm I had the same error. I downgraded to 3.13.12 in order to continue using ib_async