Timothy Lusk added the comment:
I'll admit I don't know enough about Python c extensions to make that call, but
the fact that it wasn't crashing in the protobuf extension itself during the
import but instead during the next garbage collection made me believe it was a
Python bug. Maybe
Timothy Lusk added the comment:
I've realized this might not be Python 3.7 specific, the reason protobuf is
throwing an exception during import in my above example (as well as in our
application) is because it's throwing a deprecation warning that was only
introduced in 3.7.
Python 3.6
