summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* tests: don't leak the file object returned by imp.find_module()ci-py37-dev-modeChristoph Reiter2018-08-151-2/+6
|
* tests: run our pytest excepthook plugin first to prevent warningsChristoph Reiter2018-08-151-1/+1
| | | | | Our plugin raising exceptions seems to confuse other hooks, marking it to be run first gets rid of them.
* tests: remove some leftover debug printChristoph Reiter2018-08-151-2/+1
|
* tests: silence some deprecation warnings due to ValueArray usageChristoph Reiter2018-08-151-7/+10
|
* Use timeit.default_timer() instead of the deprecated time.clock()Christoph Reiter2018-08-151-9/+9
| | | | | default_timer() gives us the most precise time information on all platforms. time.clock() will be removed with Python 3.8
* Access abc classes through the abc module with Python 3Christoph Reiter2018-08-151-3/+7
| | | | It will stop to work with Python 3.8
* ci: enable the new python 3.7 developer mode during testsChristoph Reiter2018-08-152-0/+6
|
* ci: build and run tests in the gnome master flatpak runtime. Fixes #241Christoph Reiter2018-08-152-0/+13
| | | | Allow failures for now as we don't control it and can't easily react if it breaks.
* tests: extend the meson cext import hack to _gi_cairo. Fixes #242Christoph Reiter2018-08-151-2/+2
| | | | | | | | It imports the modules directly and puts them in sys.modules under the full name. gi._gi_cairo was missing which made it import the system version (because the gi package is registered as a namespace package). Handle gi._gi_cairo there as well.
* meson: declare_dependency for use by potential superprojectsMathieu Duponchelle2018-08-151-0/+6
|
* tests: skip a cairo.Path check with older pycairo, it was added with 1.15.1Christoph Reiter2018-08-121-1/+2
| | | | Noticed because the gnome sdk image has pycairo 1.14.1
* ci: try lcov master for collection coverage on MSYS2Christoph Reiter2018-08-111-3/+3
| | | | | msys2 has updated to gcc8 and lcov can't read the resulting files. Maybe this helps.
* tests: skip a flaky test on pypy3Christoph Reiter2018-08-111-0/+1
| | | | | This sometimes segfaults on pypy3. I can't see why, so skip for now and reenable once pypy3 haa a stable release.
* Merge branch 'csoriano-master-patch-77687' into 'master'Christoph Reiter2018-07-221-2/+2
|\ | | | | | | | | glib.wrap: Update urls See merge request GNOME/pygobject!80
| * glib.wrap: Update urlsCarlos Soriano2018-07-221-2/+2
|/ | | No idea for what this is used, but the urls needs update.
* flake8: exclude meson subprojectsChristoph Reiter2018-07-201-0/+1
|
* gtktemplate: Don't error out when loading a resource that is only available ↵Christoph Reiter2018-07-201-2/+13
| | | | | | | | | | | in an overlay. Fixes #230 g_resources_get_info() doesn't do overlays but we use it to verify that the resource exists. See https://gitlab.gnome.org/GNOME/glib/issues/1445 In case g_resources_get_info() errors out check g_resources_lookup_data() before giving up. Because glib reads the overlay paths only once at start this is hard to add tests for.
* Merge branch 'convert_glib' into 'master'Christoph Reiter2018-07-111-1/+1
|\ | | | | | | | | pygi-convert: Fix some issues See merge request GNOME/pygobject!78
| * pygi-convert: Fix GLib.IOCondition regexSander Sweers2018-07-041-1/+1
| |
* | ci: python updateci-py-updateChristoph Reiter2018-07-073-8/+8
| |
* | ci: enable all CI jobs againChristoph Reiter2018-07-071-4/+0
| | | | | | | | theoretically gitlab bans should be disabled now
* | Gtk.Template: Add test for second instance initialisationKai Willadsen2018-07-071-0/+37
| | | | | | | | | | | | The attribute deletion here is the easiest way to stop current PyGObject from double-handling the initialisation in this case, which breaks the newer init_template() handling.
* | Gtk.Template: Remove init_template() from instance, not classKai Willadsen2018-07-071-1/+1
|/ | | | | | | | Without this change, the second instantiation of any templated class will fail to run any of the actual template-handling logic. This is *only* relevant when using the _gtk_template helpers with an older PyGObject; in newer versions, this method isn't called.
* pygi-convert: Enable glib conversionSander Sweers2018-07-021-7/+7
|
* pygi-convert: Remove incorrect conversionsSander Sweers2018-07-021-2/+0
|
* Update gitignore to ignore the pycairo subprojectChristoph Reiter2018-06-241-0/+1
|
* meson: fix naming/version/path of the .egg-info fileChristoph Reiter2018-06-241-3/+11
| | | | | | | | | Match what we do with distutils * Use "PyGObject" as package name (it's not case sensitive, but no need to diverge there) * Mark unstable releases as dev releases by adjusting the version number * Install in the right directory (not the gi package)
* meson: support building pycairo as a subprojectChristoph Reiter2018-06-243-3/+19
|
* Add override for GdkPixbuf.Pixbuf.new_from_data. Fixes #225pixbuf-new-from-dataChristoph Reiter2018-06-173-0/+103
| | | | | | | | | new_from_data isn't bindable (see https://bugzilla.gnome.org/show_bug.cgi?id=721497) and will result in use after free. While we could try to move people away from it and skip it in GI a github code search turns up quite a few users. This adds an override for it, wrapping GdkPixbuf.Pixbuf.new_from_bytes, and marks any usage of the callback args as deprecated.
* Update NEWSChristoph Reiter2018-05-311-0/+9
|
* gi/pygi-argument: Squash critical warning when using array as hash valuePhilip Withnall2018-05-181-0/+2
| | | | | | | | | | | | | | Using a GPtrArray as the value type of a GHashTable currently produces a warning: Unsupported type array for example when calling a function whose return type is annotated as: (transfer container) (element-type filename GPtrArray<SomeObject>) Since we don’t treat objects (GI_TYPE_TAG_INTERFACE) specially when marshalling to/from GHashTable, we shouldn’t need to treat arrays specially either. Handle the case explicitly. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* docs/getting started: add "pacman -Suy" before installing packages under msys2Christoph Reiter2018-05-161-7/+8
| | | | | | pacman doesn't support installing packages without doing a system upgrade first. In case the user already has msys2 installed but not used in a while just doing the install might not work.
* git commit -m "version bump"Christoph Reiter2018-05-162-2/+2
|
* release3.29.2Christoph Reiter2018-05-161-0/+40
|
* meson: increase the test timeoutChristoph Reiter2018-05-131-1/+2
| | | | we run the whole test suite as one test
* ci/meson: build with pypy and run testsChristoph Reiter2018-05-131-8/+11
| | | | pypy+pycairo doesn't work because it doesn't install a .pc file with it.
* README: mention that we support PyPyChristoph Reiter2018-05-131-3/+4
|
* README: remove coverage badge, gitlab can now show them on the project pageChristoph Reiter2018-05-131-5/+0
|
* ossig: Don't leak the callbacks in case the event loops are not stopped ↵sigint-fallback-leakChristoph Reiter2018-05-111-6/+9
| | | | | | | | | | through SIGINT. Fixes #219 We didn't remove them if the event loops returned normally. This also fixes a small race where a SIGINT gets ignored right after the yield check and before the old handler is reinstated. Check after the signal handler is switched back instead. This resulted in GLib.MainLoop and Gio.Aplication instances leaking.
* meson: remove subprojects we don't useChristoph Reiter2018-05-063-10/+0
|
* meson: don't autodetect pycairo support, force it and add an option to ↵Christoph Reiter2018-05-065-8/+14
| | | | | | disable it If you don't want pycairo support pass "-Dpycairo=false"
* docs: Add pycairo requires for development setupKai Willadsen2018-05-051-0/+1
|
* Merge branch 'gerror-docs' into 'master'Christoph Reiter2018-05-042-0/+49
|\ | | | | | | | | docs: Add introduction to handling GLib.Error See merge request GNOME/pygobject!69
| * docs: Fix quark_from_string/to_string confusionKai Willadsen2018-05-051-1/+1
| |
| * docs: Fix references in new error handling docsKai Willadsen2018-05-041-9/+9
| |
| * docs: Add introduction to handling GLib.ErrorKai Willadsen2018-05-042-0/+49
| |
* | Don't crash on multiple calls to GObject.Value.__del__. See !66Christoph Reiter2018-05-043-2/+16
| | | | | | | | | | | | | | | | | | After chaining up accessing anything on the instance will crash like accessing self.g_type in this case. Guard against that by exposing if the wrapped boxed is still there. Ideally we shouldn't invalidate the object in __del__, but various things depend on it atm. For another time..
* | valgrind: add some wildcards to function namesChristoph Reiter2018-05-041-1/+1
| | | | | | | | | | Debian seems to have started using LTO for Python and some symbol names have a ".lto_priv" suffix now.
* | gi/pygi-value: Don't wrap GValue in GValue when creating GValueArrayStian Selnes2018-05-043-13/+74
|/ | | | | | | | | | | | | | | | | | | | If a GValueArray is created from a list of GValues, it should not wrap these GValues in a second layer of GValues before appending to the array. The end result should be a GValueArray of GValues, not a GValueArray of GValues holding another GValue (unless the user explicitly creates such a value). With this patch the behavior is now consistent when creating a GValueArray and appending GValues directly, and creating a GValueArray within a GValue based on a list of GValues. For instance, to create a GValueArray of G_TYPE_UINT the user must create GValues manually and create a GValueArray from these. The result should be a GValueArray of GValues that hold G_TYPE_UINT, not a GValueArray that contain GValues that hold a GValue that holds G_TYPE_UINT. See !66
* importer: raise ImportError in load_module() and not find_module(). See #213Christoph Reiter2018-05-031-9/+9
| | | | | | | | | find_module() should either return None or a loader, but we raised ImportError there in case we already knew that the namespace was missing. Move that check to load_module() instead. While there shouldn't be any functional difference, raising in find_module() under Python 3 resulted in a chained exception with an unrelated error message printed first.
View Lorry Controller Status