I found just replacing the ib_insync with ib_async worked fine.? I use virtual environments so I created a new one, did pip install of async and copied the code I was using over.? I like having both since I have a ton of code that I don't want to delete, but may never use so why change it all and test.
toggle quoted message
Show quoted text
-------- Original message --------
From: "pythontrader via groups.io" <ali@...>
Date: 2025-01-15 1:24 p.m. (GMT-08:00)
Subject: [ib-async] Migration from ib_insync to ib_async
Greetings,
I am planning to migrate a code base from ib_insync to ib_async.
I would like to consult with this forum to understand the scope of the migration. Specifically, should I prepare for an extensive code migration, or is it as simple as running a pip install and replacing all imports of ib_insync with ib_async?
Thank you for your insights!
