You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for a direct TWS-connection (so non-containerized) yields an import error regarding UNSET_DECIMAL
Traceback (most recent call last):
File "<...>", line 19, in <module>
from nautilus_trader.adapters.interactive_brokers.config import IBMarketDataTypeEnum
File "<...>/lib/python3.11/site-packages/nautilus_trader/adapters/interactive_brokers/config.py", line 23, in <module>
from nautilus_trader.adapters.interactive_brokers.common import IBContract
File "<...>/lib/python3.11/site-packages/nautilus_trader/adapters/interactive_brokers/common.py", line 19, in <module>
from ibapi.common import UNSET_DECIMAL
ImportError: cannot import name 'UNSET_DECIMAL' from 'ibapi.common' (<...>/lib/python3.11/site-packages/ibapi/common.py)
where UNSET_DECIMAL is indeed not present (anymore or yet?) in said ibapi version.
Expected Behavior
No import error
Actual Behavior
Import error as described above
Steps to Reproduce the Problem
Try given example from example/ directory under given package versions (current stable versions as of today)
Specifications
WSL2/debian 12.8
Python 3.11.2
nautilus_trader 1.210.0
The text was updated successfully, but these errors were encountered:
Original constant seems to have been 'UNSET_DECIMAL = 1e10'.
It seems incompatilbity goes deeper. Follow up issue is: ImportError: cannot import name 'ListOfHistoricalSessions' from 'ibapi.common'
I will stop here in order not to spam the ticket.
Toying with package versions
nautilus-ibapi 10.19.4
nautilus_trader 1.210.0
ibapi 9.81.1.post1
and example
https://github.com/nautechsystems/nautilus_trader/blob/develop/examples/live/interactive_brokers/connect_with_tws.py
for a direct TWS-connection (so non-containerized) yields an import error regarding UNSET_DECIMAL
where UNSET_DECIMAL is indeed not present (anymore or yet?) in said ibapi version.
Expected Behavior
No import error
Actual Behavior
Import error as described above
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: