| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
When marshalling a GValue array to C, the GValue items are copied into a C
GValue array, not a C GValue pointer array. _pygi_marshal_from_py_array()
already calls the cleanup_func for the original item;
_pygi_marshal_cleanup_from_py_array() must not do it again, as this would try
to g_slice_free the array item.
https://bugzilla.gnome.org/show_bug.cgi?id=672224
|
|
|
|
|
|
|
|
|
|
|
|
| |
Renamed to match the rest of the class names in GObject and also
not clobber the builtin python property.
Keep the old "property" identifier for backwards compatibility
for now.
https://bugzilla.gnome.org/show_bug.cgi?id=672168
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For GValues we cannot just copy the GValue memory in
_pygi_marshal_from_py_array(), as the from_py_cleanup() function clears and
releases the GValue and with it its v_pointer. Use g_value_copy() to copy by
value instead.
This uncovered another bug in _pygi_marshal_cleanup_from_py_array(): It always
assumed that C arrays contained pointers, but this is not the case for GValue
arrays: these are actual struct arrays, not struct pointer arrays (cf. their
construction in _pygi_marshal_from_py_array()). Check if an array contains
pointers or values and compute the correct array item pointer for both cases.
Also add a corresponding test case for marshalling GValue arrays from C back to
Python, which works fine.
https://bugzilla.gnome.org/show_bug.cgi?id=672065
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to make sure that all Gtk.Dialog subclasses inherit from
the overridden Window class. For that to be done automaticly we need
to create the Window class before the Dialog class.
Now when it's inherited properly we need to avoid calling the Window
constructor twice as it passes in a construct-only parameter. So add
**kwargs to the Window constructor to allow us to pass in any kind
of GObject property to it and refactor the Dialog subclasses to pass
in all properties to the same constructor.
Also adds a bunch of tests to make sure that the hiearchy is correct.
https://bugzilla.gnome.org/show_bug.cgi?id=672158
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The python 'property' class allows for decoration of methods using
.getter and .setter. These were added as methods to the GObject.property
class to match that of the python property class and allow for decoratored
setter methods.
In addition, __call__ was added to allow an instantiated decorator with
args to also decorate a method:
class C(GObject.GObject):
_value = 0
@GObject.property(type=int, default=0)
def propInt(self):
return self._value
@propInt.setter
def propInt(self, value):
self._value = value
https://bugzilla.gnome.org/show_bug.cgi?id=586181
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
|
|
|
|
| |
Adds argument that makes them compatible with PyGTK.
https://bugzilla.gnome.org/show_bug.cgi?id=672045
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=668903
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
|
|
|
|
|
|
|
|
| |
Bump gobject-introspection dependency to ensure that we have the corresponding
changes in g-i.
https://bugzilla.gnome.org/show_bug.cgi?id=668903
Signed-off-by: Michel Dänzer <michel@daenzer.net>
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
|
|
|
|
| |
Just like IconView.
https://bugzilla.gnome.org/show_bug.cgi?id=671409
|
|
|
|
|
| |
When we found the member, unref the objects before breaking out of the
loop.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This complements the already existing test for a "transfer container" return
array. We can't verify the internal refcount as these arrays get marshalled
internally, but at least we can verify that it does not crash due to
double-free.
|
|
|
|
| |
Not necessary any more since glib 2.24, and we depend on 2.31.
|
|
|
|
|
| |
Use g_get_real_time() instead as recommended by the documentation. This also
simplifies the code.
|
|
|
|
| |
Replace with _schar(). We depend on glib >= 2.31 already.
|
|
|
|
|
| |
Looking at the gir file gtk.gdk.x11_* should get converted to
GdkX11.x11_*. Fixing pygiconvert.sh to do so.
|
|
|
|
| |
Commit ee62df4d2fc0cc63c2f29d3ad9b47b875dbd5f89 introduced both calls
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=649267
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=664496
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=668356
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
|
|
| |
Use what was recently added in g-i
|
|
|
|
| |
Also tidy up the spacing a bit
|
| |
|
|
|
|
|
|
|
|
| |
All GtkBuilder signals are presently being connected 'after', ignoring
what is specified in the builder XML. This is due to an obvious logic
error.
https://bugzilla.gnome.org/show_bug.cgi?id=669705
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=669598
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gspawn 'argv' and 'envp' parameters expect sequences of strings. This
is enforced by checking that the passed argument is a sequence and that
each item returned from it is a string.
We do now, however, verify that each item can be successfully taken from
the sequence. 'os.environ' is an example of an object that passes
PySequence_Check() but fails to return objects from PySequence_ITEM().
Add a simple NULL check to avoid the crash.
https://bugzilla.gnome.org/show_bug.cgi?id=669594
|
| |
|
| |
|
|
|
|
|
|
| |
project
Removed obsolete MAINTAINERS file
|
|
|
|
|
|
| |
This reverts commit 654711d0f940d7480d0f1cdb25a3dc9996f7a706.
Due to this commit breaking backwards compatability, we decided to revert this change
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=664150
|
|
|
|
|
|
|
| |
This fixes a crash in test_gi.TestGPtrArray and makes sure
memory is free'd correctly
https://bugzilla.gnome.org/show_bug.cgi?id=669393
|
|
|
|
|
|
|
| |
This models the case where the callback is successful and does not set
an error.
https://bugzilla.gnome.org/show_bug.cgi?id=669415
|
|
|
|
|
|
|
|
|
|
| |
Commit adcfe96d49b09bc accidentally dropped the check if *error is NULL, i. e.
any error is actually set. Due to that, pyglib_error_check() always returned
TRUE. Reintroduce the check.
Thanks to Alberto Mardegan for spotting this!
https://bugzilla.gnome.org/show_bug.cgi?id=669415
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=663288
|
|
|
|
|
|
| |
when unused
https://bugzilla.gnome.org/show_bug.cgi?id=665553
|
|
|
|
|
|
|
|
| |
Defines __nonzero__ (python2) and __bool__ (python3) for GLib.Variant
Also adds some tests for boolean comparisons.
https://bugzilla.gnome.org/show_bug.cgi?id=647723
|
|
|
|
|
|
|
|
|
| |
Define __hash__, __eq__, __ne__ for GLib.Variant so that objects can
be used in sets, dicts, and can be compared using == and != easily.
Also adds some tests for this.
https://bugzilla.gnome.org/show_bug.cgi?id=647725
|
|
|
|
|
|
| |
Change test_everything.TestCallbacks.* test names from camelCase to the
standard PEP-8 underscore_style. This is now consistent with all other test
case names.
|
|
|
|
|
|
| |
This triggered a -Wmissing-braces warning.
https://bugzilla.gnome.org/show_bug.cgi?id=668497
|
|
|
|
|
|
| |
This squashes a compiler warning.
https://bugzilla.gnome.org/show_bug.cgi?id=668497
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In a couple of cases, the variable in question was set to a value
spelled out again later in the function.
The 'sequence_cache' variable is re-declared five lines below.
The return value of 'read' was previously completely ignored. The
'gssize ret' variable was in fact added to squash an unused-result
warning.
https://bugzilla.gnome.org/show_bug.cgi?id=668497
|
|
|
|
|
|
|
|
| |
To allow for the common syntax:
object.connect('signal-name', main_loop.quit)
https://bugzilla.gnome.org/show_bug.cgi?id=668288
|
|
|
|
|
|
| |
https://bugs.gentoo.org/show_bug.cgi?id=321879
https://bugzilla.gnome.org/show_bug.cgi?id=666852
|
|
|
|
|
|
|
|
| |
The marshaller previously ignored "transfer full" on GError* arguments, causing
crashes due to double-freeing them. This causes the testCallbackUserdata() test
case to crash after the previous GError/GHashTable marshalling fix.
https://bugzilla.gnome.org/show_bug.cgi?id=666270
|
|
|
|
|
|
|
|
|
|
|
| |
Marshalling of these types from C is already implemented, let's take it
into use for calbacks and closures too.
Add corresponding test cases.
https://bugzilla.gnome.org/show_bug.cgi?id=666270
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|