| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Since we now target Python 3.8+, looking at Debian and Ubuntu releases
we have 1/2.64 in Ubuntu 20.04 and 1/2.66 in Debian bullseye.
Go with the older one of the two.
|
|
|
|
|
|
|
| |
Otherwise we get:
tests/meson.build:124:15: ERROR: Unknown variable "pycairo_dep".
See !216
|
|
|
|
|
| |
We now require 1.60.0, to unconditionally use the GI_CHECK_VERSION
version check macro.
|
|
|
|
| |
This allows importing gi module from within meson devenv.
|
|
|
|
|
|
|
|
|
|
| |
Python 3.7 will be EOL in 3 months, so before the next release.
* Update the Python versions in the CI images
* Bump the docker base image from focal to jammy to test against a newer stack.
This triggers new deprecation warnings which we need to disable for now.
* Bump the old docker based image to from buster to bullseye, moving
from Python 3.7 to 3.9.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
0.53.0 targets Ubuntu 20.04, also matches what pycairo needs currently.
Update the libffi wrap to match what glib uses (the old one no longer
works with current glib)
And target pycairo main (we target main for everything else too..)
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
The meson_options.txt file uses the "feature" option which was
introduced in 0.47.0.
|
| |
|
| |
|
|
|
|
|
|
|
| |
It results in crashes downstream (pulls in a meson fallback in gst-ci)
and it isn't really needed, so revert for now.
Also Fedora only has 3.1 it turns out.
|
|
|
|
|
|
| |
Motivated by the EOL of Python 3.5 and the EOL of Ubuntu 16.04 next year
this requires Python 3.6 and moves all other dependencies to what is available in
Ubuntu 18.04.
|
| |
|
| |
|
|
|
|
| |
So user have more control on whether to build it or not
|
|
|
|
| |
Depend on setuptools to make sure we write out requires-python in all cases
|
| |
|
| |
|
|
|
|
| |
Fixes #363
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
Currently, there is no way to prevent tests from building using meson.
When cross-compiling, building the tests aren't necessary, and would require
gobject-introspection also to be made with tests.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
All the rest of the Python code ends up in arch'd directories, except
for the .egg-info directory, which should do the same.
|
| |
|
|
|
|
|
| |
It's the one shipped with Ubuntu 16.04, which is the oldest distro
we run tests on.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Check for the Cairo headers and libraries on Visual Studio builds if the
pkg-config files could not be found, as we don't have direct control
over the build system for Cairo/Cairo-GObject for Visual Studio.
Also, don't add gcc/CLang-specific compiler flags for Visual Studio
builds, but just force-include msvc_recommended_pragmas.h, which is
shipped with GLib, which should make the compiler-time checks that we
really want to look out for.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It contains more strict checks which might be useful for finding potential bugs.
Initialize PyGILState_STATE because gcc can't figure out that state is always
defined in the release case when Py_DEBUG is enabled..
Remove -Winline which is triggerd for pygobject_init() with the debug build.
Not sure what to do when inlining fails, so just remove the warning for now.
|
| |
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
| |
|
|
|
|
|
|
| |
disable it
If you don't want pycairo support pass "-Dpycairo=false"
|