Gtk+-2.0 crashes because you do something wrong. Granted, it would
nice that Gtk didn't segfault, but neither PyGTK nor Gtk ever have
given any strict guarantees that erroneous programs don't crash. Either
the bug should be closed, or marked as enhancement with minor
severity. It's up to the
Closing then, the Ubuntu team is already overworked, you can open a bug
on bugzilla.gnome.org if you want
** Changed in: gtk+2.0 (Ubuntu)
Importance: Undecided = Wishlist
Status: Unconfirmed = Rejected
--
buggy PyGTK code crashed the python 2.5 interpreter run via the terminal
reassign to gtk+2.0, or should this be in the python bindings?
** Changed in: gtk+2.0 (Ubuntu)
Sourcepackagename: python2.5 = gtk+2.0
--
buggy PyGTK code crashed the python 2.5 interpreter run via the terminal
https://bugs.launchpad.net/bugs/104980
You received this bug notification because
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7229193/CoreDump.gz
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7229194/Disassembly.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7229195/ProcMaps.txt
** Attachment added:
