videoflow package

Subpackages

Submodules

videoflow.cli module

Moved to videoflow.deploy.cli.

This module remains as a permanent compatibility shim: the videoflow console script resolves videoflow.cli:main, and an installed entry point outlives the source tree it was generated from. Do not add code — edit videoflow/deploy/cli.py instead.

videoflow.compile module

Moved to videoflow.deploy.compile.

This module remains as a permanent compatibility shim: videoflow deploy spawns python -m videoflow.compile inside the solution image, so the host CLI and the image can be different videoflow versions in either direction and the old path must keep resolving. Do not add code — edit videoflow/deploy/compile.py instead.

videoflow.provision module

Moved to videoflow.runtime.provision.

This module remains as a permanent compatibility shim: python -m videoflow.provision is rendered into the provision init Job of every deployed flow, and those manifests may already be applied in a cluster. Do not add code — edit videoflow/runtime/provision.py instead.

videoflow.serialization module

Moved to videoflow.wire.serialization.

This module remains as a permanent compatibility shim: the wire format is the one thing a message outlives its producer on, so external importers may have pinned this module path, and it must keep resolving to the wire codec. Do not add code — edit videoflow/wire/serialization.py instead.

videoflow.version module

videoflow.worker module

Moved to videoflow.runtime.worker.

This module remains as a permanent compatibility shim, and is the most frozen path in the package: python -m videoflow.worker is the ENTRYPOINT baked into the published base images, inherited by every contrib component image, and spawned by the local engine. Already-built images cannot be retargeted. Do not add code — edit videoflow/runtime/worker.py instead.