I haven't done anything to pygobject in the last 8 years, and forgot everything. I have no authority over this right now.

Thibault Saunier authored Mar 29, 2022 and Nirbheek Chauhan committed Apr 14, 2022

When the interface is being registered by PyGObject and again through
an override, the first one is being leaks, free it at this point.

We need to copy the GInterfaceInfo to set on the GType QData as we
do not own it.

Up until now pycairo provided a cairo.get_include() helper which
could be used to find the required include directory matching the module,
considering various scenarios.

Starting with 3.8 this leads to problems on Windows since CPython on Windows
will no longer use PATH for the DLL lookup and expects the library user to
explicitely pass the directory where the cairo DLL can be found.

In a build environment the user has no control over this though, so we have to
find the include directory without loading/importing pycairo again.

This now uses a combination of importlib.util.find_spec() for finding the module
and importlib.metadata.distribution() for finding the package version.

Hopefully this covers all cases.

Python 3.8 no longer uses PATH for searching DLLs so we have to
add them manually.

Note that unlike PATH add_dll_directory() has no defined order,
so if there are two same DLLs in PATH we might get a random one.

This only makes sure that 'setup.py test' and 'pytest' continue working.
If you include pygobject manually you have to call os.add_dll_directory()
yourself with the location of the DLLs you ship.

The test_gvalue_gobject_ref_counts appears to be working just fine these
days.

PyList_GET_ITEM only returns a borrowed reference. In the unlikely event
of an error converting the key or value, the reference would be
unintentionally decremented. This could cause random failures later on
(and was indeed causing the PyPy test to fail randomly later on).

Arjan Molenaar authored Sep 14, 2021 and Christoph Reiter committed Mar 28, 2022

Check for required type, instead of negating invalid type.

Arjan Molenaar authored Aug 03, 2021 and Christoph Reiter committed Mar 28, 2022

Why does a g_instance_init() function only handle GObjects?

Zev Lee authored May 13, 2021 and Christoph Reiter committed Mar 28, 2022

Add Hello World GTK under Other Options and Passphraser as an example that uses the aforementioned build system.

So it uses a newer sphinx

newer pycoverage supports lcov as output format, so convert
to lcov and only generate one report at the end for everything.

The lcov report isn't that nice, but at least everything is in one place.

Arjan Molenaar authored Nov 03, 2021 and Christoph Reiter committed Mar 27, 2022

It's not used in GTK 4.

Arjan Molenaar authored May 19, 2021 and Christoph Reiter committed Mar 27, 2022

Those methods require a Gdk.ContentFormats object.

An attempt to pass a Path object as a filename results in a TypeError:
"Must be bytes, not PosixPath". A simple way to accept Path objects
would be unconditionally turning them into strings, but since native
paths may be bytes as well, this might break applications relying on
being able to bytes-based filename. Instead, convert the path into an
appropriate representation (string or bytes) using os.fspath(). It
internally tests whether the path is a PathLike object and does the
right thing.
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

They moved away from bitbucket some time ago.

In theory it should no longer be needed, but PyPy hasn't
updated this part of their implementation yet, and not initing
threads will lead to crashes due to missing GIL init.

If it triggers it creates a blocking GUI dialog without any helpful output.
I can't reproduce the cause on my local machine, just on the CI server, so
jsut disable this for now.

There are some glib deprecations that need fixing, but let's get
CI green again first.

GObject Introspection renamed its default development branch to
"main".

Mathieu Duponchelle authored Dec 04, 2019 and Thibault Saunier committed Dec 06, 2021

If C code calls g_object_new() for a GInitiallyUnowned subclass
implemented in python, the expectation is to receive a floating
reference.

The solution is used is the same picked for
5efe2e5c, this is simply a special
case that was omitted at the time.

Emmanuele Bassi authored Jul 29, 2021 and Christoph Reiter committed Sep 19, 2021

If gobject-introspection adds a new scope that we do not handle, we
should definitely not error out. Printing out a critical warning and
asking to file an issue should be enough.

Miro Hrončok authored May 18, 2021 and Christoph Reiter committed Sep 19, 2021

On Python 3.10, the code raised an ImportWarning:

    ImportWarning: DynamicImporter.find_spec() not found; falling back to find_module()

See https://docs.python.org/3.10/whatsnew/3.10.html#deprecated

> Starting in this release, there will be a concerted effort to begin cleaning
> up old import semantics that were kept for Python 2.7 compatibility.
> Specifically, find_loader()/find_module() (superseded by find_spec()),
> load_module() (superseded by exec_module()), module_repr()
> (which the import system takes care of for you),
> the __package__ attribute (superseded by __spec__.parent),
> the __loader__ attribute (superseded by __spec__.loader),
> and the __cached__ attribute (superseded by __spec__.cached)
> will slowly be removed (as well as other classes and methods in importlib).
> ImportWarning and/or DeprecationWarning will be raised as appropriate to help
> identify code which needs updating during this transition.

Fixes https://gitlab.gnome.org/GNOME/py...

It got renamed in gtk 4.1.0, see gtk@a1216599
To avoid an API break and make porting easier provide both versions for
all users.

Fixes #467

Tested with 4.2 and 1.0 and things loog good

It will be EOL before the next release.
This means Ubuntu 18.04 (without backports) is no longer supported,
we will move to Debian Buster as the new oldest tested target.