Timothy Lusk <tl...@carbonblack.com> 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 doesn't cause any warnings importing protobuf so it doesn't abort the import. Might need a different test case to confirm what versions this does apply to. I've made a change to our application's error handling in this area so we aren't having a segfault anymore, but this is still a bug in Python itself. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37434> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
