What would mean that ValueError in connect?
The correct fix I guess is stop using the GObject API for discovering
which signals a GObject subclass has and instead rely on the
introspection API. Then we could mark as introspectable=0 all such
signals and you would get a 'Signal not known' error on
pygtk still shouldn't core dump the interpreter ;) but i guess this is a
bug for upstream to fix. It should probably raise a ValueError on the
.connect() call.
--
PyGtk App Core dumps
https://bugs.launchpad.net/bugs/638513
You received this bug notification because you are a member of Ubuntu
Bug
for future reference, 'value-changed' is the correct signal to use
--
PyGtk App Core dumps
https://bugs.launchpad.net/bugs/638513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
ok, so you're not supposed to use "input" from Python ... according to the
documentation:
The "input" signal is emitted when the value changes. The value_ptr is a
GPointer to the value that cannot be accessed from PyGTK. This signal cannot be
handled in PyGTK.
d'oh
** Changed in: glib2.0 (Ubun
(gdb) bt
#0 0x760d1953 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#1 0x760d2353 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#2 0x7492380c in gtk_spin_button_update () from
/usr/lib/libgtk-x11-2.0.so.0
#3 0x74926008 in ?? () from /usr
** Changed in: glib2.0 (Ubuntu)
Status: New => Confirmed
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => Medium
--
PyGtk App Core dumps
https://bugs.launchpad.net/bugs/638513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
The crash is result of callback not returning expected value (or, as in
our examples not returning nothing at all). Python should still handle
it more gracefully.
--
PyGtk App Core dumps
https://bugs.launchpad.net/bugs/638513
You received this bug notification because you are a member of Ubuntu
B
A smaller python script that reproduces this crash
** Attachment added: "spin.py"
https://bugs.edge.launchpad.net/ubuntu/+source/glib2.0/+bug/638513/+attachment/1629399/+files/spin.py
--
PyGtk App Core dumps
https://bugs.launchpad.net/bugs/638513
You received this bug notification because yo
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
--
PyGtk App Core dumps
https://bugs.launchpad.net/bugs/638513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
** Description changed:
- Step:
+ Steps:
1. expand the attached crash_repro directory that has the repro code
- 2. run the "grid_filter.py" file
- (note that if you have quickly-widgets installed, you need to make sure that
you point your python path to the
+ 2. run the "grid_filter.py" file
** Attachment added: "core dump file"
https://bugs.edge.launchpad.net/ubuntu/+source/glib2.0/+bug/638513/+attachment/1585828/+files/core
--
PyGtk App Core dumps
https://bugs.launchpad.net/bugs/638513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "crash_repro.tar.gz"
https://bugs.edge.launchpad.net/bugs/638513/+attachment/1585821/+files/crash_repro.tar.gz
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/638513/+attachment/1585822/+files/Dependencies.txt
--
PyGtk App Core dumps
htt
12 matches
Mail list logo
