Notice
This project has evolved into IB-insync and all development is happening there now.
To port code:
TWSClient has moved to ib_insync.client.Client (with much improvements);
TWSClientQt: The new Client can be used with PyQt and quamash.
Introduction
The tws_async package allows the Python API from Interactive Brokers (IBAPI) to be used asynchronously and single-threaded with the asyncio standard library or with the PyQt5 framework.
This offers a simpler, safer and more performant approach to concurrency than multithreading.
Installation
Install using pip:
pip3 install -U tws_async
Note that on some systems the pip3 command is just pip.
Python version 3.5 or higher is required as well as the Interactive Brokers Python API.
Usage
This package offers two clients that can be used as a drop-in replacement for the standard EClient as provided by IBAPI:
TWSClient, for use with the asyncio event loop;
TWSClientQt, for use with the PyQt5 event loop.
These clients also inherit from ibapi.wrapper.EWrapper and can be used exactly as one would use the standard IBAPI version. The asynchronous clients use their own event-driven networking code that replaces the networking code of the standard EClient, and they also replace the infinite loop of EClient.run() with an event loop.
To simplify working with contracts, this package provides Contract, Stock, Option, Future, Forex, Index, CFD and Commodity classes that can be used anywhere where a ibapi.contract.Contract is expected. Examples of some simple cases are Stock('AMD'), Forex('EURUSD'), CFD('IBUS30') or Future('ES', '201612', 'GLOBEX'). To specify more complex contracts, any property can be given as a keyword.
To learn more, consult the official IBAPI documentation or have a look at these sample use cases:
Historical data downloader
The HistRequester downloads historical data and saves it to CSV files; histrequester demo illustrates how to use it.
Realtime streaming ticks
The tick streamer subscribes to realtime tick data.
Jupyter Notebook
To use the Interactive Brokers API fully interactively in a Jupyter notebook, have a look at the example notebook.
Jupyter can be started with the command jupyter notebook.
This notebook uses the Qt version of the client, where the Qt event loop is started with the %gui qt5 directive at the very top. It is not necessary to call the run() method of the client.
Notes on using asycio in a notebook
Currently there does not seem to be a single-threaded way to directly run the asyncio event loop in Jupyter. What can be done is to use the Qt event loop (which does have good integration with the Jupyter kernel) with the quamash adaptor. With quamash the Qt event loop is used to drive the asyncio event loop. This can be done by placing the following code at the top of the notebook:
%gui qt5
import asyncio, quamash
loop = quamash.QEventLoop()
asyncio.set_event_loop(loop)
One thing that does not work in the combination of quamash and Jupyter is the loop.run_until_finished method. It can be patched like this:
def run_until_complete(self, future):
future = asyncio.ensure_future(future)
qApp = qt.QApplication.instance()
while not future.done():
qApp.processEvents(qt.QEventLoop.WaitForMoreEvents)
return future.result()
quamash.QEventLoop.run_until_complete = run_until_complete
The asyncio version of the client relies on loop.run_until_finished to connect synchonously. So in order to run the asyncio client in the notebook, apply the patch or just connect asynchonously (i.e. give asyncConnect=True to the connect call).
Changelog
Version 0.5.7
HistRequester fix for endDateTime formatting
Version 0.5.6
HistRequester updated to version 9.73.04 of the API
Version 0.5.5
small simplifications
Version 0.5.4
connect() call of the clients will now by default block until client is ready to serve requests.
getReqId() method added to both clients.
dataHandlingPre() and dataHandlingPost() event hooks added to clients.
logging added.
util module aded.
file tws_async.py renamed to twsclient.py, tws_asyncqt.py to twsclientqt.py.
Version 0.5.3
Added optional asyncConnect argument to client.connect() method. The default is now to connect synchronously (block until connected).
Fixed bug in HistRequester when downloading daily data.
Version 0.5.0
Initial pip package release.
Good luck and enjoy,
- author:
Ewald de Wit <ewald.de.wit@gmail.com>
Metadata
Release files for tws-async 0.5.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tws_async-0.5.7-py3-none-any.whl | Python 3 | none | any | Details |
Release files / tws_async-0.5.7-py3-none-any.whl
| Download URL | tws_async-0.5.7-py3-none-any.whl |
|---|---|
| Size | 25.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
937d88d936e7233082b1e1068ab1cfdf7c2438e40e76ca89e4039c45618a5f5a
|
|
BLAKE2b-256 checksum How to use checksums |
302ef2eb8002b07976aa91f408a97e9ce8172c525183a89488e21fe51a053860
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tws-async 0.5.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.