| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This depends on whether CSD is used or not and theme related things.
We only know for sure that it's larger than the inlcuded button.
Fixes the test suite under wayland.
|
| |
|
|
|
|
|
|
|
|
|
| |
It gets used by pip>=9 to decide which version from pypi to install. Which means we can
more easily drop older Python versions without having to worry about breaking anyones setup.
Sadly our oldest supported system, Ubuntu Xenial, only has pip 8, so it will install
the newest version and fail anyway if we drop Python 3.5 support. We can at least
point users to update their pip in their virtual environments then.
https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
|
| |
|
|
|
|
|
|
| |
The headers of Python 3.8 trigger the warning and PEP7 states that
Python is depending on this now.
As far as I remember this was mostly added to keep the code compatible
with ancient py2 MSVC, so only use it with Python 2.
|
| | |
|
| |
|
|
|
|
| |
It was only used with Python 2 and unused/reserved with Python 3.
Python 3.8 has renamed the slot and is now using it for something different
which breaks our build.
|
| | |
|
| |
|
|
| |
It doesn't support gcc9 yet
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We did not free the array passed to us after marshalling, only the helper garray.
Patch by Tomasz Miąsko
|
| |
|
|
|
|
|
|
|
| |
It returned NULL in case no error was set or if creating the error
result failed and this wasn't checked by the callers.
Change it to return Py_None in case no error was set and NULL in
case of an error. In pygi_error_check() we can't really forward the
error, so just print it and raise RuntimeError instead.
|
| |
|
|
|
|
| |
Suppresses spammy output. We'll still get output for
scanner warnings and failures, just don't output
anything any longer when everything's fine.
|
| |
|
|
|
|
| |
Currently, there is no way to prevent tests from building using meson.
When cross-compiling, building the tests aren't necessary, and would require
gobject-introspection also to be made with tests.
|
| |
|
|
|
|
|
|
| |
These files had contributions from Thibault Saunier, Aurelien Jarno,
Mathieu Duponchelle and me. All agreed to provide their contribution under
the LGPLv2.1+, see #320 for details.
This makes the file licenses match the project license.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Real changes here: https://github.com/pygobject/pygobject-travis-ci-examples/commit/6a462f528
This gives us a newer gtk/pygobject so update the version info in the docs.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
So that there is a clear path on what to do after successfully getting the
example app running.
|
| |
|
|
| |
It can use pycairo as a subproject now
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Sometimes the CI machines are slow
|
| |
|
|
|
| |
Installing in a virtualenv is quite common and it's not clear what the
build dependencies needed are.
|
| |
|
|
| |
Everyone should start with Python 3 nowadays.
|
| |
|
|
|
|
|
|
|
| |
gtk crashes if gtk_init() fails and we can't do much about it.
This assumes the Gtk.Window() is the first instantiated widget and
raises an exception in case init failed.
We already had such a check but it was removed in 86a37d67455d
for some reason (maybe because it only helps in some cases)
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Install .egg-info directory to arch'd dir.
See merge request GNOME/pygobject!109
|
| |/
|
|
|
| |
All the rest of the Python code ends up in arch'd directories, except
for the .egg-info directory, which should do the same.
|
| |
|
|
|
|
| |
Gtk.Builder.get_objects(). Fixes #287
With gnome master things have changed (I assume due to glib hashing changes)
|
| |
|
|
|
|
|
|
| |
As pointed out in #85 we don't use strip_boolean_result() for the main
Gdk.Event struct while we do for the member structs.
But at this point int time I'm afraid that changing it will break existing code,
so just add some tests to document the difference and make sure it doesn't change.
|
| |\
| |
| |
| |
| |
| |
| | |
gio overrides: emit a warning when creating various dbus types without a constructor. Fixes #15
Closes #15
See merge request GNOME/pygobject!107
|
| | |
| |
| |
| |
| |
| |
| |
| | |
constructor. Fixes #15
We zero slice allocate them and the boxed copy/free functions don't handle that.
They just use ref counting which leads to double free because we start with a zero
refcount and the free funcs use g_free() while we allocate it with g_slice_alloc().
|
| | |
| |
| |
| |
| |
| |
| | |
It's a bit faster and is a good chance to make sure both marshalling
paths behave the same and add some tests.
No functional change intended.
|
| | |
| |
| |
| | |
set_string() allows it too
|
| | |
| |
| |
| |
| | |
It already allows everything which can be passed to bool() except None.
I don't see a good reason for that so allow None as well.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The field marshalling code is slow and doesn't do any caching at all
which in turn makes accessing Value.g_type slow.
Add a static helper function for fetching the GType and use that instead.
This reduced the time for creating a GValue + setting it by ~30%
|
| | | |
|