summaryrefslogtreecommitdiff
path: root/PKG-INFO.in
Commit message (Collapse)AuthorAgeFilesLines
* Drop Python 3.7 support and update CI envsChristoph Reiter2023-03-191-1/+1
| | | | | | | | | | 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.
* Drop support for Python 3.6Christoph Reiter2021-09-191-1/+1
| | | | | | 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.
* Drop Python 3.5 support and bump other dependenciesdrop-py35Christoph Reiter2020-09-141-1/+1
| | | | | | 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.
* Remove Python 2 supportChristoph Reiter2020-03-081-1/+2
| | | | Depend on setuptools to make sure we write out requires-python in all cases
* PKG-INFO: add an lgplv2+ license classifierChristoph Reiter2018-11-271-1/+1
| | | | | It is displayed on PyPI and this makes it clear that it isn't v3 and has the "or later" clause.
* PKG-INFO: Revert name back to PyGObjectChristoph Reiter2017-12-101-1/+1
| | | | | | | | | My thinking there was that it gives us the same naming of tarballs as with the autotools build system. But on a second thought, we can't use the same tarball anyway due to gz vs xz and while the naming should be case insensitive it's not worth the risk. The commit changing it was 3e455944f5835c7509
* setup.py: Remove various classifiers and the download-url which aren't ↵Christoph Reiter2017-12-091-5/+0
| | | | | | accepted by pypi pypi does not allow uploading packages with these set, so remove them altogether.
* setup.py: Port to distutils/setuptoolsChristoph Reiter2017-12-061-4/+4
| | | | | | | | | | | | | | | | | | | Instead of wrapping autotools add a proper setuptools based build system. Compared to the autotools one this does not install .pc files or headers and does not allow running tests. It uses pkg-config for discovering dependencies and explictely searches for .pc files in the Python prefix so that pycairo installations in a virtualenv are discovered. When using MSVC, pkg-config is skipped and it is assumend that INCLUDE and LIB is properly set up. Version information and requirements are parsed from configure.ac, package metadata is parsed from PKG-INFO.in. Also adds a "setup.py distcheck" command which makes sure all tracked files end up in the tarball and that the tarball builds (no tests are run atm). https://bugzilla.gnome.org/show_bug.cgi?id=789211
* Change maintainer in PKG-INFO to selfSimon Feltman2014-07-311-2/+2
|
* Remove last GIO-related bitsSimon van der Linden2011-02-111-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=638899
* Update, add glib/gio bindings and other environmentsJohan Dahlin2008-07-261-1/+4
| | | | svn path=/trunk/; revision=864
* Split out PyGObject from PyGTK.Johan Dahlin2006-01-091-0/+22