summaryrefslogtreecommitdiff
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* Require glib 2.64 and g-i 1.64HEADmasterChristoph Reiter2023-05-131-2/+2
| | | | | | 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.
* Bump up the requirement to gobject-introspectionEmmanuele Bassi2023-05-131-1/+1
| | | | | We now require 1.60.0, to unconditionally use the GI_CHECK_VERSION version check macro.
* version bumpChristoph Reiter2023-03-191-1/+1
|
* release3.44.0Christoph Reiter2023-03-191-1/+1
|
* version bumpChristoph Reiter2023-01-281-1/+1
|
* release3.43.1Christoph Reiter2023-01-281-1/+1
|
* interface: Fix leak when overriding GInterfaceInfoThibault Saunier2022-04-141-0/+5
| | | | | | | | 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.
* setup.py: look up pycairo headers without importing the moduleChristoph Reiter2022-04-131-47/+31
| | | | | | | | | | | | | | | | | | 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.
* version bumpChristoph Reiter2021-09-191-1/+1
|
* release3.42.0Christoph Reiter2021-09-191-1/+1
|
* version bumpChristoph Reiter2021-03-191-1/+1
|
* release3.40.0Christoph Reiter2021-03-191-1/+1
|
* Revert the dependency bump for libffiChristoph Reiter2020-09-151-1/+1
| | | | | | | 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.
* Drop Python 3.5 support and bump other dependenciesdrop-py35Christoph Reiter2020-09-141-4/+4
| | | | | | 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.
* Update NEWS and bump versionChristoph Reiter2020-09-121-1/+1
|
* Remove all Python 2 Python codeChristoph Reiter2020-04-151-21/+2
|
* Remove Python 2 supportChristoph Reiter2020-03-081-18/+8
| | | | Depend on setuptools to make sure we write out requires-python in all cases
* version bumpChristoph Reiter2020-03-081-1/+1
|
* release3.36.0Christoph Reiter2020-03-081-1/+1
|
* Drop Python 2 support on WindowsChristoph Reiter2019-10-051-0/+3
| | | | Fixes #363
* version bumpChristoph Reiter2019-09-091-1/+1
|
* release3.34.0Christoph Reiter2019-09-091-1/+1
|
* version bumpChristoph Reiter2019-08-181-1/+1
|
* 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
* build: don't use -Wdeclaration-after-statement with Python 3Christoph Reiter2019-06-071-1/+5
| | | | | | | | 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-071-5/+1
|
* Update NEWS; version bumpChristoph Reiter2019-03-101-1/+1
|
* version bumpChristoph Reiter2019-03-071-1/+1
|
* version bumpChristoph Reiter2019-02-021-1/+1
|
* version bumpChristoph Reiter2018-12-151-1/+1
|
* setup.py: Print an install command hint when pkg-config is missingChristoph Reiter2018-12-081-3/+26
|
* setup.py: fix typoChristoph Reiter2018-11-201-5/+5
|
* build: bump glib requirement to 2.48Christoph Reiter2018-11-201-1/+1
| | | | | It's the one shipped with Ubuntu 16.04, which is the oldest distro we run tests on.
* version bumpChristoph Reiter2018-11-171-1/+1
|
* setup.py: Make it possible to build without cairo through an env var. See #250Christoph Reiter2018-11-131-2/+4
| | | | | | | | | PYGOBJECT_WITHOUT_PYCAIRO=1 python3 setup.py install or with a recent pip: PYGOBJECT_WITHOUT_PYCAIRO=1 pip3 install --no-build-isolation pygobject I don't see a nice way for telling pip not to require pycairo, so this will have to do for now.
* setup.py: Enable tests to run on MSVC buildsChun-wei Fan2018-11-101-48/+93
| | | | | | This enables the test command to be also usable on Visual Studio builds, where we allow the test DLLs and .gir/.typelib's and test Python modules to be built on Visual Studio builds as well.
* setup.py: Fix MSVC buildsChun-wei Fan2018-11-101-68/+75
| | | | | | | | | | | The distutils C Compiler object for MSVC does not have a compiler sub-attribute, so check the compiler type before we try to use that sub-attribute. This will fix builds on MSVC using distutils. Also, in place of checking the various GCC/CLang compiler flags for compile-type warnings we want to look out for, force-include msvc_recommended_pragmas.h when we are building with Visual Studio, as we are doing in the other GNOME projects, to achive similar effects.
* Revert "setup.py: skip adding gcc warnings flags with msvc. Fixes #275"Christoph Reiter2018-11-101-3/+0
| | | | This reverts commit f7503c4cd1c03fde215024e61db9e1a439f39997.
* setup.py: skip adding gcc warnings flags with msvc. Fixes #275Christoph Reiter2018-11-101-0/+3
| | | | | | The compiler.compiler attribute isn't available with msvc and errors out. The warning flag detection code only works with gcc style compilers anyway so just skip it with msvc.
* Sort input file listBernhard M. Wiedemann2018-10-201-1/+1
| | | | | | | so that _gi.so builds in a reproducible way in spite of indeterministic filesystem readdir order See https://reproducible-builds.org/ for why this is good.
* setup.py: make it possible to disable cairo/pycairo support. See #250Christoph Reiter2018-09-161-33/+50
| | | | | | There is no non-hacky way to make this configurable for users so this just makes it work depending on a global variable. At least this makes it easy to patch.
* revert closure typecasts from commit 25a5b066 See #247Dan HorĂ¡k2018-09-141-1/+1
|
* version bumpChristoph Reiter2018-08-311-1/+1
|
* release3.30.0Christoph Reiter2018-08-311-1/+1
|
* version bumpChristoph Reiter2018-08-161-1/+1
|
* ci: build python 2.7 and 3.7 in debug mode. Fixes #243ci-debug-buildChristoph Reiter2018-08-161-1/+0
| | | | | | | | | | 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.
* git commit -m "version bump"Christoph Reiter2018-05-161-1/+1
|
* build: disable new cast-function-type warnings with gcc8Christoph Reiter2018-05-031-0/+1
| | | | | We have to assign PyCFunctionWithKeywords functions to PyCFunction fields everywhere, so not much we can do. Ideas welcome.
* setup.py: dedup some of the compiler input argsChristoph Reiter2018-04-231-4/+9
| | | | reduces the output at build time a bit
* setup.py: fix distcheckChristoph Reiter2018-04-201-3/+3
| | | | Add all the meson related files to the manifest