It should indeed be done like this:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
from gi.repository import GObject
mystore = Gtk.ListStore(GObject.TYPE_UINT64)
mystore.insert_with_valuesv(-1, [1], [GObject.Value(GObject.TYPE_UINT64,
1330400507426)])
###
I
"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
It works!
On 09.03.20 21:17, Sebastien Bacher wrote:
> COuld you test the upstream workaround and use
> GObject.Value(GObject.TYPE_UINT64, 1330400507426) ?
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in
COuld you test the upstream workaround and use
GObject.Value(GObject.TYPE_UINT64, 1330400507426) ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1866625
Title:
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
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
--
6 matches
Mail list logo
