You need to handle the exception that might be thrown here.

Some of our proposed deployment use cases do not include a LibG deployment. Ideally we wouldn't like the Python nodes to break, just because LibG isn't around :-)