After a deeper analysis and some trial+error I have now a working 
containerd Python API package. Bottom line was to comb through the process 
of generating a proper .proto files file structure of only those including 
vendored dependencies needed and then fixing the import paths to avoid any 
import path aliasing. The details can be found here: 
https://github.com/TheDiveO/pycontainerd/blob/master/script/genpb2.sh ... 
heavens, that containerd API and vendor tree really is ... challenging ... 
when generating Python modules.

As I can work with the unmodified existing containerd sources, I can now 
send a PR upstream to the Python containerd package project.

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/ffa453d3-9291-444a-ae9c-9144d7070a18n%40googlegroups.com.

Reply via email to