[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

[Timothy Lusk]

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 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 
<https://bugs.python.org/issue37434>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37434] Segfault in typeobject.c at _PyObject_GC_UNTRACK(type)

[Timothy Lusk]

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 that's not a correct assumption though.

--
nosy: +Timothy Lusk2

___
Python tracker 
<https://bugs.python.org/issue37434>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com