request.security()` — Work in Progress

A highly requested feature is now in active development. Each security context runs as its own OS process with a separate Python interpreter, so there’s no global state collision and multi-core parallelism comes for free. Processes communicate via shared memory with near-zero
overhead. The same compiled code runs in both chart and security contexts — lib.close automatically resolves to the current context’s close. Only lookahead_off is supported (by design — live trading must never see future data).

(Resolved in v6.4.0)

This website uses cookies and similar technologies. By continuing to use the site, you accept this. Details in our Privacy Policy.