Winding back up to <@U06A03HV1>'s mention of go 1....
# general
e
Winding back up to @witty-crayon-22786's mention of go 1.5 `.so`s and python - I would definitely support an effort to link the python backend to the go backend (and c++ backend) via a 'c-shared-lib' product dependency and a standard installed noop provider of that product.