- Apr 27, 2024
-
-
Calling PyLong_AsLong resurrects the underlying python object again, which is something that PyPy is not liking. In addition to this, the code would call g_spawn_close_pid twice if the user did explicitly call the close method. This method does not make any sense, but it is exported already so probably should be left as-is. Add an internal copy of the GPid to the object that is set to 0/NULL when it is closed. Having this both avoids the double close_pid call and also avoids the need of resurrecting the object when freeing it.
-
The test checks what happens if python garbage collects the source when the dispatch function returns. However, pypy will not (reliably) collect the object at that point, rendering the test non-functional.
-
It appears that PyObject_ClearWeakRefs may only be called on PyPy if there are actually weak references to the object. Note that to correctly track that, one also needs a separate weaklist to store them. Add a weaklist entry, setup the tp_weaklistoffset and only call PyObject_ClearWeakRefs if there are weak references. Also add a test that actually uses weak references to ensure it doesn't crash either.
-
Otherwise the object will not have been finalized and the print did not yet happen when checked.
-
This makes `Gio.File` a `PathLike` object, allowing the use of `open()`. Signed-off-by: Christoph Matthias Kohnen <christoph.kohnen@disroot.org>
-
-
-
Arjan Molenaar authored
Co-Authored-By: Frederic Martinsons <frederic.martinsons@unabiz.com>
-
- Apr 25, 2024
-
-
Woodrow Douglass authored
-
- Apr 18, 2024
-
- Apr 13, 2024
-
-
-
Meson-python will take the version from `meson.build`.
-
- Apr 11, 2024
-
-
Arjan Molenaar authored
-
Arjan Molenaar authored
Use GObject.ParamSpec instead.
-
Arjan Molenaar authored
-
Arjan Molenaar authored
-
Arjan Molenaar authored
Hopefully GParamSpec is the only special case in the core libraries.
-
Arjan Molenaar authored
Not used in our code, nor tested.
-
Arjan Molenaar authored
-
- Apr 06, 2024
-
-
Christoph Reiter authored
-
- 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.
-
Handle no-arguments check in init function instead of new.
-
See #624.
-
This implementation causes trouble when initialized with the new fundamental type support.
-
- Mar 25, 2024
-
-
Chris Mayo authored
Installing a .dist-info directory containing just METADATA is compliant: https://packaging.python.org/en/latest/specifications/recording-installed-packages/#the-dist-info-directory
-
Christoph Matthias Kohnen authored
Adds an override for `Gio.DataInputStream` to enable line iteration using the iter protocol. Signed-off-by: Christoph Matthias Kohnen <christoph.kohnen@disroot.org>
-
- Mar 23, 2024
-
-
Arjan Molenaar authored
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.
-
- Mar 10, 2024
-
-
Christoph Reiter authored
3.8 will be EOL 2024-10, so around the time of the next release.
-
Christoph Reiter authored
-
- Mar 09, 2024
-
-
Christoph Reiter authored
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
-
Christoph Reiter authored
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
-
Christoph Reiter authored
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.
-
Christoph Reiter authored
-
Christoph Reiter authored
-
- Feb 20, 2024
-
-
Arjan Molenaar authored
They tend to raise OSErrors.
-
- Feb 15, 2024
-
-
- Feb 12, 2024
-
-
Christoph Reiter authored
-
Christoph Reiter authored
-