Running Interactive Brokers with native Python support seems to be a pain in the ass. As I see it, I will continue with the methodologies I show in my Interactive Brokers API course. It seems that using Python 3 on Mac is a real pain so I am not bothered to fully implement or install until there is an official document to show to to implement. It seems that this current API version is not fully stable but only experimental.
What I will do
As for me, I will continue with the same path in using Redis NOSQL for the central data hub. We can connect Redis with either C++ or Java to interface with Interactive Brokers Treader Workstation (TWS). I shall stick with this for many reasons as we currently sit.
I have included some useful URL tips if you are interested. Pleaseunderstand I get frustrated with all these unofficial ways to implement. I will just stick with the current non Python techniques I have.
I am sure this will get hammered out over the next few months. Note that this API client release (with the Python client) is not stable. As a result, I will not even enter the fray of playing around with this until there is a stable release you can download.FACEBOOK ACCOUNT and TWITTER. Don't worry as I don't post stupid cat videos or what I eat!