Python & SDK
Python environment and SDK management
Check the bundled runtime, bind a project and understand SDK update availability.
Check the environment
- Open Quantitative Trading → Environment & Settings. Review the Python version, SDK revision and validation state.
- Run the available validation and FQE connection checks. Investigate a failed state before starting a Python project.
- Select a validated environment for the project. Confirm an explicit version switch; canceling must preserve the existing binding.
Export the SDK for an external editor
Use Export Python SDK to copy the validated SDK into a new destination folder. This exports source, type assets, packaging metadata and license for development. It is not a global Python installation and does not automatically install third-party requirements. Project source import/export is separate from SDK export.
Understand update status
Check SDK releases in the environment page. “No independent release available” is different from a failed installation. The bundled runtime follows application updates. Independent signed-release installation depends on a compatible release and trusted signature configuration; a staged download is not an installed environment. Switching the default environment does not migrate an already-running task.
For the current Desktop workflow. Labels and available capabilities can vary by application version and connected provider.