osmose.engine_capabilities

Pure, browser-free description of what each engine produces for a config, and of what each engine offers the UI.

Single source of truth for the Run-page capability panel and for every “does this engine do X” question a page asks. No Shiny imports; the engine dependencies are the two block-reason functions (pure) and the C# engine’s availability check, which loads nothing.

There are three engines, so “not Python” does not mean Java. A page asks by name: is_java(), is_in_process(), engine_supports().

Module Attributes

ENGINE_MODES

The values of AppState.engine_mode, and how the UI names them.

Functions

describe_engine(engine, config[, jar_version])

Describe what engine will produce for config.

engine_label(mode)

The engine's name as the UI shows it.

engine_supports(mode, feature)

Whether the engine mode offers the UI feature.

is_in_process(mode)

An engine that runs inside this process, on a worker thread: Python or C#.

is_java(mode)

The Java engine: a subprocess behind osmose.runner, with a jar and Java options.

Classes

EngineCapability(engine, can_run, ...)