After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 699096 - Use correct class for GtkEditable's get_selection_bounds() function
Use correct class for GtkEditable's get_selection_bounds() function
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: introspection
unspecified
Other All
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-28 06:48 UTC by Mike Ruprecht
Modified: 2013-04-28 13:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Use correct class for GtkEditable's get_selection_bounds() function (927 bytes, patch)
2013-04-28 06:48 UTC, Mike Ruprecht
committed Details | Review

Description Mike Ruprecht 2013-04-28 06:48:48 UTC
When calling get_selection_bounds() on a GtkEntry I get the following assertion:
TypeError: unbound method get_selection_bounds() must be called with TextBuffer
Comment 1 Mike Ruprecht 2013-04-28 06:48:50 UTC
Created attachment 242701 [details] [review]
Use correct class for GtkEditable's get_selection_bounds() function
Comment 2 Mike Ruprecht 2013-04-28 06:53:28 UTC
I should add this hasn't been tested with a full pygobject build, but instead I edited my debian experimental version's (3.8.1-1) installed copy, tested, and diffed it.
Comment 3 Mike Ruprecht 2013-04-28 06:59:44 UTC
I should add this hasn't been tested with a full pygobject build, but instead I edited my debian experimental version's (3.8.1-1) installed copy, tested, and diffed it.
Comment 4 Martin Pitt 2013-04-28 13:09:17 UTC
Comment on attachment 242701 [details] [review]
Use correct class for GtkEditable's get_selection_bounds() function

Ouch, thanks for spotting this! Applied to master and 3.8 branch, so that this will get fixed in 3.8.2.