summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* tests: don't use strict mode for xfail with the excepthook pluginChristoph Reiter2020-03-141-1/+1
| | | | | This no longer works since pytest 5.4.0. Somehow the xfail gets checked before the plugin runs so errors thrown in the plugin get ignored.
* Remove Python 2 supportChristoph Reiter2020-03-089-47/+26
| | | | Depend on setuptools to make sure we write out requires-python in all cases
* Add .mypy_cache to .gitignoreChristoph Reiter2020-03-081-0/+1
|
* version bumpChristoph Reiter2020-03-082-2/+2
|
* release3.36.0Christoph Reiter2020-03-083-2/+19
|
* CI: use the "flatpak" tag for jobs using flatpakChristoph Reiter2020-02-211-0/+4
|
* CI: update pip in the xenial jobChristoph Reiter2020-02-151-0/+1
| | | | | Some packages have started failing to install with the pip shipped with xenial.
* Doc: Remove reference to a fixed bugChristian Stadelmann2020-01-251-3/+0
|
* meson: track pycairo-1.18 branch in the pycairo subprojectChristoph Reiter2020-01-241-1/+1
| | | | It still supports Python 2
* CI: install pycairo from pypi not git masterChristoph Reiter2020-01-242-4/+2
| | | | master has dropped Python 2 support
* gtk overrides: Drop Menu, MenuItem for Gtk 4Marinus Schraal2020-01-211-8/+8
| | | | These API's have been removed (gtk commit 7ee5779efcf5).
* pygobject-object: Avoid checking whether NULL is floatingAlexandru Băluț2020-01-203-1/+25
| | | | This issue was introduced in a102f046a178472278522e3e9d7c0b40ecd52ade.
* CI: Update interpretersChristoph Reiter2019-12-303-19/+19
|
* Add Gaphor to Who is Using PyGObjectDan Yeaw2019-12-281-0/+1
| | | | Signed-off-by: Dan Yeaw <dan@yeaw.me>
* Update openSUSE instructionsWouter2019-12-281-1/+1
| | | More packages are required to be able to run the example on the getting started page on openSUSE
* coverage: add coverage context for each jobChristoph Reiter2019-12-275-8/+11
|
* CI: make things work with coverage.py 5.xChristoph Reiter2019-12-275-4/+20
| | | | | | It has changed its internal format to sqlite and still doesn't provide a way to merge runs from different OSes, see https://github.com/nedbat/coveragepy/issues/903
* Revert "CI: pin coverage.py version to 4.x, we don't support 5.x yet"Christoph Reiter2019-12-204-4/+4
| | | | This reverts commit 5a3033d8e249ad4a739a65bc49cc1c2a4cb142b9.
* CI: pin coverage.py version to 4.x, we don't support 5.x yetChristoph Reiter2019-12-174-4/+4
| | | | | The saved format has changed and we currently depend on it for merging Windows and Unix paths.
* Add Girens by 'Who Is Using PyGObject'Tijder2019-11-241-0/+1
|
* tests: set NO_AT_BRIDGEChristoph Reiter2019-11-161-0/+3
| | | | | Otherwise we get "Couldn't register with accessibility bus" warnings which break the tests.
* CI: Use gnome-master for testing with gtk4Christoph Reiter2019-10-1910-95/+53
| | | | | | | | This makes it easier to track upstream changes without us having to rebuild docker images. Downside is that we don't control it and API is still changing, so allow the job to fail.
* CI: update interpretersChristoph Reiter2019-10-183-14/+14
|
* CI: switch the xenial test job to Python 3Christoph Reiter2019-10-084-6/+6
| | | | | This job tests our oldest supported setup. Switch it to Python 3 so we can drop Python 2 support.
* Drop Python 2 support on WindowsChristoph Reiter2019-10-053-14/+7
| | | | Fixes #363
* Port to g_object_new_with_properties()Christoph Reiter2019-10-043-37/+87
| | | | | | | | g_object_newv() and GParameter are deprecated now. Replace all GParameter usage with a separate GValue and char* array and add a compatibility function for g_object_new_with_properties() that also works with older glib and converts things back to GParameter.
* Avoid various new glib deprecation warningsChristoph Reiter2019-10-045-9/+26
| | | | | This should make things build with -Werror again once we port things to g_object_new_with_properties()
* Make pygobject_prepare_construct_properties() staticChristoph Reiter2019-10-042-5/+1
| | | | It's not used anywhere else atm
* version bumpChristoph Reiter2019-09-092-2/+2
|
* release3.34.0Christoph Reiter2019-09-093-2/+8
|
* version bumpChristoph Reiter2019-08-182-2/+2
|
* release3.33.1Christoph Reiter2019-08-181-0/+9
|
* Make PyGIDeprecationWarning always inherit from DeprecationWarningChristoph Reiter2019-08-181-10/+0
| | | | | | | | | | | To make deprecation warnings more visible we made it inherit from RuntimeWarning with unstable releases and DeprecationWarning for stabel releases. This is a bit confusing when being flooded with warnings when testing under jhbuild etc. Also recent pytest has changed to show deprecation warnings triggered during tests, so the warnings should be more visible now for devs using pytest. This changes it to inherit from DeprecationWarning always again.
* pygobject-object: fix refcount of floating return valuesMathieu Duponchelle2019-08-114-1/+68
| | | | | | | | | When g_signal_emitv returns a floating reference as the return value, which we end up ref_sinking, do not unset the GValue, as we've taken ownership from it and don't want it to drop its reference. Adds a test that highlights the issue
* pygobject: ignore GParameter deprecationsChristian Hergert2019-08-061-0/+2
| | | | | | | Consumers of this API will get GParameter notifications elsewhere in their code when using GParameter. Since it needs to be around for compatibility API, we can safely ignore it here and save consuming applications some duplicated deprecation warnings.
* variant: Create a tuple directlyMathieu Bridon2019-07-231-3/+2
| | | | | | This avoids iterating twice: once to create the list with a list-comprehension and a second time to transform that list into a tuple.
* variant: Define the LEAF_ACCESSORS globallyMathieu Bridon2019-07-231-17/+18
| | | | | | | | This saves a bit of work, instead of defining the dictionary every time the method is called. Unpacking many GVariants in a loop, this shaved roughly 17% of the total time.
* variant: Get the type string only once when unpackingMathieu Bridon2019-07-231-7/+9
| | | | | This saves a bit of work. Unpacking many GVariants in a loop, this shaved roughly 6% of the total time.
* Update NEWSChristoph Reiter2019-06-231-0/+8
|
* test_overrides_gtk: be less strict re gtk window heightsChristoph Reiter2019-06-231-5/+1
| | | | | | | 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.
* setup.py: add python_requiresChristoph Reiter2019-06-161-0/+2
| | | | | | | | | | | 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
* Update NEWSChristoph Reiter2019-06-161-0/+9
|
* build: don't use -Wdeclaration-after-statement with Python 3Christoph Reiter2019-06-072-2/+11
| | | | | | | | 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.
* build: drop some checks for unsupported Python versionsChristoph Reiter2019-06-072-11/+2
|
* Don't use PyTypeObject.tp_print with Python 3Christoph Reiter2019-06-071-1/+4
| | | | | | 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.
* tests: remove usage of time.clock(), no longer available in py3.8Christoph Reiter2019-06-071-3/+3
|
* CI: Add a python 3.8-dev jobChristoph Reiter2019-06-072-0/+6
|
* CI: disable lcov under MSYS2Christoph Reiter2019-06-071-6/+7
| | | | It doesn't support gcc9 yet
* docs: getting started: default to mingw64 for the MSYS2 instructionsChristoph Reiter2019-05-171-2/+2
| | | | | | | | | The idea was to default to mingw32 because mingw64 builds had more bugs initially and if one wants to bundle things mingw32 makes it run on more machines. But, the gtk stack should be in good shape now with mingw64 and people tend to prefer 64bit builds (see #326 and #321) ignoring the docs, so lets just default to mingw64 instead.
* ci: work around pip3 install --user not working in recent fdo-sdkChristoph Reiter2019-05-171-0/+3
| | | | https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/776
View Lorry Controller Status