Comment 2 for bug 1866625

I'm not sure what exactly they are really talking about at
https://gitlab.gnome.org/GNOME/pygobject/issues/198.

My FR concerns 3.26.1-2ubuntu1 and at gitlab it is stated "I think it
used to work in 3.26." which

clearly is not the case.

I took a look into the source and in pygi-value.c I found this:

case G_TYPE_INT:
    {
        glong val = PYGLIB_PyLong_AsLong(obj);
        if (val == -1 && PyErr_Occurred ())
            return -1;
        if (val > G_MAXINT || val < G_MININT) {
            PyErr_SetString(PyExc_OverflowError, "out of range for int
property");
            return -1;
        }
        g_value_set_int(value, (gint)val);
        break;
    }

and a lot of comments like this:

#if PY_VERSION_HEX < 0x03000000

[snip]

#endif

To me this means that somebody is/was aware of the fact that some more
work has to be done for

making this stuff compatible to Python 3.

On 09.03.20 14:48, Sebastien Bacher wrote:
> Thank you for your bug report, that seems similar to
> https://gitlab.gnome.org/GNOME/pygobject/issues/198
>
> ** Bug watch added: gitlab.gnome.org/GNOME/pygobject/issues #198
> https://gitlab.gnome.org/GNOME/pygobject/issues/198
>
> ** Changed in: pygobject (Ubuntu)
> Importance: Undecided => Low
>