Closes #629.

Arjan Molenaar authored Feb 20, 2024 and Dan Yeaw committed Apr 13, 2024

Meson-python will take the version from `meson.build`.

Use GObject.ParamSpec instead.

Hopefully GParamSpec is the only special case in the core libraries.

Not used in our code, nor tested.

Arjan Molenaar authored Mar 23, 2024 and Christoph Reiter committed Apr 05, 2024

This should prevent primitive (non-instantiatable) types
from being derived from Fundamental.
Those are -- in the case of GStreamer -- wrapped by Python classes
anyway.

Arjan Molenaar authored Mar 23, 2024 and Christoph Reiter committed Apr 05, 2024

Handle no-arguments check in init function instead of new.

Arjan Molenaar authored Mar 23, 2024 and Christoph Reiter committed Apr 05, 2024

See #624.

Arjan Molenaar authored Mar 23, 2024 and Christoph Reiter committed Apr 05, 2024

This implementation causes trouble when initialized
with the new fundamental type support.

Installing a .dist-info directory containing just METADATA is compliant:

https://packaging.python.org/en/latest/specifications/recording-installed-packages/#the-dist-info-directory

Adds an override for `Gio.DataInputStream` to enable line iteration
using the iter protocol.

Signed-off-by: Christoph Matthias Kohnen <christoph.kohnen@disroot.org>

For 3.48.1, tests are disabled by default, since tests require a
(development) dependency on GI apps.

When working on PyGObject, you want to have tests enabled, though.

3.8 will be EOL 2024-10, so around the time of the next release.

In case meson-python is invoked via pip, any Python tools it uses
can't access the system Python packages, which breaks g-ir-scanner,
which we use for building the tests.

Fix by not building tests when building a wheel.

See https://github.com/mesonbuild/meson-python/issues/596

Fixes #622

After !301 the pypy version has a different pip version compared to the
oder pyenv cpython installations and also its pip installs to the system
which comes with new restrictions with newer pip (requires --break-system-packages).

To make the test environment for all interepreter versions the same create
and active a venv first and also update pip in there.

This is motivated by the pip in 22.04 not supporting "--config-settings",
which is required in !302

As pointed out in !299 the libffi shipped with the portable pypy version
conflicts with the system libffi, and could lead to crashes.

Instead of the pyenv version just use the official PPA which contains
a pypy linked against system libs. That has the downside that the version
is no longer pinned and docker image rebuilds will lead to newer pypy versions
being included.

They tend to raise OSErrors.

We create an sdist using meson for GNOME, and one
using meson-python for PyPI.

This is similar to what we did with setuptools for the last
releases. The main thing here is the automation, everything else,
like version numbers, formats etc is open for debate.