nixl-python-api

To write a minimal NIXL Python API transfer safely, you must provide readiness evidence like installed package versions and validate backend memory types before generating transfer code. This prevents speculative transfers when environment or backend evidence is missing.

NIXL Python agent setup or metadata exchange fails when backend evidence gaps or memory descriptor readiness issues exist. You must collect installed package evidence and validate backend readiness before the lifecycle reference file routes correct setup instructions.

Security invariants for NIXL descriptor and metadata bytes require treating all bytes as untrusted, avoiding public exposure of listener ports, and preventing unsafe deserialization or raw-address construction. These trust-boundary rules protect control-plane setup.

To handle NIXL transfer polling and cleanup in custom Python code, load the minimal matching reference file for transfer polling and cleanup. Ensure you validate backend and memory-type readiness first, as the API gates guidance on environment evidence.

You can use NIXL Python API with incomplete version or backend plugin evidence, but it classifies the issue as version/source uncertainty and withholds transfer code. Readiness-gated guidance prevents unsafe transfers until backend evidence is validated.