"int" maps to the same underlying type in Python 2 and Python 3. This
wasn't changed when pygobject was ported to Python 3 and can't really be
changed now. If you want be sure your numbers fit use the suggested
"GObject.TYPE_*", or just use "object" which means the Python int object
is stored as
>From an pygobject upstream POV this cycle hasn't seen any high risk
changes, so +1 from me in case that helps :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1819183
Title:
New 1.57.3 g-i tarball is out.
For the apport thing (I'm not sure if this is relevant in your build
environment):
https://gitlab.gnome.org/GNOME/pygobject/commit/d9ddad7bcac86d37a9010c8cd529a0e6ca1a9f48
PyGObject tests might still fail because of
We do test against gnome master now with gitlab-CI, so hopefully this
will be noticed earlier in future releases.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1787474
Title:
I think this is https://gitlab.gnome.org/GNOME/gobject-
introspection/commit/1f5c81048d762f4866137e1e3221d85b9b611d8b which
isn't in a release yet. I'll ask for a release.
I also noticed that the pygobject test suite fails due to sys.excepthook
== apport_excepthook, I'll look into that.
--
You
This crash seems to be limited to Ubuntu 12.10 and 13.04 (looking at the
duplicates and the linked upstream bug report). And that's no longer
supported.
Also the affected program is unmaintained for some years now.
** Changed in: pygobject (Ubuntu)
Status: Triaged => Fix Released
--
You
PyGObject warns that gi.require_version() wasn't used. That's something
that needs to be fixed by the library user.
** Changed in: pygobject (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
