Currently the cuVS Python API wraps the resources in a dedicated Resources object. It itself uses C functions to manage the lifetime of a RAFT resource. These C functions also serve in other programming languages bindings. But, in the specific case of Python, allowing pylibraft handles to serve as resources across the cuVS Python API would allow more uniformity with the rest of the RAPIDS ecosystem.
Currently the cuVS Python API wraps the resources in a dedicated Resources object. It itself uses C functions to manage the lifetime of a RAFT resource. These C functions also serve in other programming languages bindings. But, in the specific case of Python, allowing pylibraft handles to serve as resources across the cuVS Python API would allow more uniformity with the rest of the RAPIDS ecosystem.