Bug#671785: python-gtk2: crashes reportbug on Linux with GLib >= 2.41, or kFreeBSD

[Simon McVittie]

retitle 671785 python-gtk2: crashes reportbug on Linux with GLib >= 2.41, or kFreeBSD
thanks

On Sun, 30 Dec 2012 at 20:21:30 -0600, Jeff Epler wrote:
> But whether that
> is the case or not, pygtk really can't impose the additional requirement
> on users of raw_input() that they have to manipulate a gdk lock before
> the call; whatever it's doing had better be transparent to users of
> raw_input.

Indeed. Having just done basically the same analysis for #758619
(which is the same locking error manifesting on Linux due to GLib 2.41
having better checks similar to those in kFreeBSD, and is currently RC),
I think pygtk's PyOS_InputHook is fundamentally flawed.

I can't think of a solution to this in pygtk, other than to disable the
PyOS_InputHook by default or entirely (which would be a feature regression
for users of the interactive Python prompt; but then again, its locking
is broken anyway).

pygobject does not appear to have that "feature".

I have reassigned #758619 back to reportbug and suggested that the
reportbug maintainers should explicitly turn off the PyOS_InputHook,
which would work around this bug for reportbug.

    S