Sorry for reviving an old thread. I just figured out what this error means after many hours of digging, and it frustrates me that I couldn't find good documentation on the error itself. This seems like a very easy mistake to make.
None is a special, global object. What "deallocating None" means is that the reference count on "None" has reached 0, and None is to be deallocated (AKA deleted). This is a bad thing! It likely means that a Python library written in C/C++ is returning Py_None for use in Python proper without first calling Py_INCREF(Py_None). The error then shows itself elsewhere in code because the ref count on None is now 1 too few. When someone throws away its reference to None, only then will this error present itself. It may or may not be a problem in GLib.py if this is the case.
None is a special, global object. What "deallocating None" means is that the reference count on "None" has reached 0, and None is to be deallocated (AKA deleted). This is a bad thing! It likely means that a Python library written in C/C++ is returning Py_None for use in Python proper without first calling Py_INCREF(Py_None). The error then shows itself elsewhere in code because the ref count on None is now 1 too few. When someone throws away its reference to None, only then will this error present itself. It may or may not be a problem in GLib.py if this is the case.
