@vivek - That is not the issue. time module is available. The earlier crash code was because a None was being returned instead an object of type 'time'. I fixed the code to handle that and print a proper error message.
You can look at the error log…
My environment:
python2.7
websocket-client==0.44.0
kiteconnect==3.5 (though, not using in my current code)
I am running 5 instances of same codebase to track 5 different scripts and do "paper trading" on each. In each instance, I establish a webso…
@sujith Happened again today, here is the log from all callback functions
2017-07-31 09:15:04, on_connect
2017-07-31 10:46:01, on_error, Connection is already closed.
2017-07-31 10:46:02, on_reconnect
2017-07-31 10:46:03, on_connect
2017-07-31 12:4…
To clarify further, at present I am just using live Tick data to do "paper trading" of my strategy. No orders are being hit. So, I don't need to login to Kite and hence not yet using KiteConnect. Code is entirely based on capturing ticks and simulat…
@sujith I am not using KiteConnect module. Only using WebSocket module.
kws = WebSocket(api_key, access_token, userID)
kws.on_error = on_error
def on_error(error, ws):
print error.message
Is this good enough?
I know for sure that the code …
@sujith - Any relevant portion you would need to see? Asking since code base is large.
Running websocket on MCX instruments. Code works fine starting 10am. But, connection seems to develop issue between 16:30 and 17:30. 3rd day straight.
I am logg…
"Continuous futures historical data"
@Kailash - What can we expect in this? Would you give data for expired series and how far back will this be supported?
