commit 863124b6268d1ea2c649d27771813c27cc9faa06 Author: Martin Pitt Date: Mon Oct 14 12:51:44 2013 +0200 release 3.10.1 NEWS | 8 ++++++++ 1 file changed, 8 insertions(+) commit 43ac1f9fd4b1f5132b7fa996da7e307371d11bb1 Author: Nuno Araujo Date: Fri Oct 11 18:41:48 2013 +0200 Fix TypeError when setting drag target_list to None When calling Widget.drag_dest_set_target_list(None) or Widget.drag_source_set_target_list(None) a "TypeError: 'NoneType' object is not iterable" is thrown. According to Gtk documentation [1] [2], this shouldn't be the case since client code should be able to pass NULL in calls made to gtk_drag_dest_set_target_list and gtk_drag_source_set_target_list. We now check if the target_list is None and do not try to create a TargetList if it is the case. [1] https://developer.gnome.org/gtk3/3.10/gtk3-Drag-and-Drop.html#gtk-drag-dest-set-target-list [2] https://developer.gnome.org/gtk3/3.10/gtk3-Drag-and-Drop.html#gtk-drag-source-set-target-list https://bugzilla.gnome.org/show_bug.cgi?id=709926 gi/overrides/Gtk.py | 4 ++-- tests/test_overrides_gtk.py | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) commit 90beeee7600bf39768c38bcfc47582c0e592eec9 Author: Simon Feltman Date: Tue Oct 1 17:09:39 2013 -0700 Use qdata for wrapper retrieval in toggle reference notifications Replace usage of user data holding PyGObject wrappers in toggle ref notifications with GObject qdata retrieval. This fixes thread safety issues where a toggle notify may be called from another thread during the PyGObject wrappers dealloc. In this case the toggle notify is blocked because the GIL is held in dealloc, and when it continues, the user data would be holding an invalid PyGObject wrapper. Using qdata solves this by ensuring the wrapper retrieval is done within the safety of the GIL and may turn up as NULL. https://bugzilla.gnome.org/show_bug.cgi?id=709223 gi/_gobject/pygobject.c | 21 ++++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) commit 073f3870f2671a387d99529bab386f2218f44e2e Author: Simon Feltman Date: Thu Oct 3 19:25:34 2013 -0700 Fix memory leak for caller allocated GValue out arguments Swizzle the order of type checks in _cleanup_caller_allocates so G_TYPE_VALUE arguments are checked before G_TYPE_BOXED. The ordering is important because G_TYPE_VALUE is a sub-type of boxed and so its specialized cleanup code was never being called (g_value_unset). Additionally update check to use g_type_is_a instead of a compare to handle the potential case of a G_TYPE_VALUE sub-type. https://bugzilla.gnome.org/show_bug.cgi?id=709397 gi/pygi-marshal-cleanup.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) commit 8e774e61d62c82efa3d907c1201359121878b4b5 Author: Simon Feltman Date: Mon Sep 23 03:57:03 2013 -0700 configure.ac: post-release bump to 3.10.1 configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)