summary refs log tree commit diff
path: root/pkgs/development/python-modules/pycairo/default.nix
Commit message (Collapse)AuthorAge
* python3.pkgs.pycairo: 1.20.0 -> 1.20.1Alyssa Ross2021-06-17
|
* pythonPackages.pycairo: requires Python 3.6+Robert Schütz2021-04-12
| | | | See https://pycairo.readthedocs.io/en/latest/changelog.html#v1-20-0.
* python3Packages.pycairo: 1.18.2 -> 1.20.0Jonathan Ringer2021-04-03
|
* Recover the complicated situation after my bad mergeVladimír Čunát2020-10-26
| | | | | | | | | | | | | | | | | I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state
* Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát2020-10-25
| | | | | | | I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
* python3.pkgs.pycairo: clean upJan Tojnar2020-10-20
| | | | | | | | * drop unneeded xlibs dependency * correct license * do not use pkgconfig alias * use pytestCheckHook * format
* python: remove isPy33, isPy34Pavol Rusnak2020-05-04
|
* treewide: Per RFC45, remove all unquoted URLsMichael Reilly2020-04-10
|
* python3Packages.pycairo: 1.18.1 -> 1.18.2Jonathan Ringer2019-11-05
|
* pythonPackages.pycairo: 1.18.0 -> 1.18.1worldofpeace2019-04-24
| | | | https://pycairo.readthedocs.io/en/latest/changelog.html#v1-18-1
* pythonPackages.pycairo: 1.16.3 -> 1.18.0worldofpeace2019-01-10
| | | | Changelog: https://pycairo.readthedocs.io/en/latest/changelog.html
* python.pkgs.pycairo: 1.15.4 → 1.16.3Jan Tojnar2018-04-12
|
* pythonPackages.pycairo: 1.10.0 → 1.15.4Jan Tojnar2017-11-27
|
* misc pkgs: Basic sed to get fix `pkgconfig` and `autoreconfHook` `buildInputs`John Ericson2017-09-21
| | | | Only acts on one-line dependency lists.
* pycairo: fix #26475 - another dead patch downloadVladimír Čunát2017-06-09
|
* pycairo: fix #26475 - a dead patch downloadVladimír Čunát2017-06-09
|
* Python: add pname attributes to librariesFrederik Rietdijk2017-05-27
| | | | so that we can use the update script.
* pycairo: fix build with Python 3.6Vaibhav Sagar2017-04-01
| | | | | Apply the same patch as for Python 3.5 so that this builds correctly. Addresses #24501.
* Python: replace mkPythonDerivation with buildPythonPackage and format="other";Frederik Rietdijk2017-03-21
| | | | | This way all Python packages use the same function, `buildPythonPackage`.
* pythonPackages.pycairo: fix nameFrederik Rietdijk2016-12-10
|
* pythonPackages.pycairo: python.is_py3k was removedFrederik Rietdijk2016-10-18
|
* pythonPackages: use mkPythonDerivationFrederik Rietdijk2016-09-01
|
* pycairo: enable for python35Alexander Ried2016-04-29
| | | | | The patch was taken from FreeBSD, it is also used on debian. see: https://svnweb.freebsd.org/ports/head/graphics/py3-cairo/files/pycairo-1.10.0-waf-py3_5.patch?revision=401900&view=markup
* pycairo: add darwin to meta.platformsVincent Laporte2016-01-28
|
* python pycairo: add python.libPrefixFrederik Rietdijk2015-12-11
|
* pycairo: disable on py35Domen Kožar2015-11-08
|
* x11: replace its usage by xlibsWrapper directlyVladimír Čunát2015-09-15
| | | | | | Scilab note: the parameters already had pointed to nonexistent dirs before this set of refactoring. But that config wasn't even used by default.
* Revert "pycairo: set user-agent to fix download of patches"Pascal Wittmann2015-04-28
| | | | | | This commit was should fix issue #7586, but it does not. This reverts commit e1c65ddfe11c8070dda00a66f2b4ae45bbddb0bc.
* pycairo: set user-agent to fix download of patchesPascal Wittmann2015-04-28
|
* Revert "Mark many packages (mostly python) broken because of broken ↵Domen Kožar2015-02-25
| | | | | | | | dependencies." This reverts commit bf86758a42f7db8c1710f1226162d9e3b6c5e9e6. See 71a9aa10ca25f5659a657d8910e11f36c3439a36
* Mark many packages (mostly python) broken because of broken dependencies.Peter Simons2015-02-23
|
* fix a bunch of packages with lua5_1Domen Kožar2014-09-10
|
* pycairo: fix for python-3.4 by LFS patchesVladimír Čunát2014-05-20
| | | | Fixes #2693.
* pycairo: Update to 1.10.0 and support both python 2 and python 3Linquize2014-02-22
| | | | Close #1802.
* pycairo: move to pythonPackagesFlorian Friesdorf2013-01-11
|
* * Reverted most of the recent Python refactorings, as discussed. It'sEelco Dolstra2010-04-21
| | | | | | | | | | | a worthy goal to move the Python packages that are currently in all-packages.nix into a single attribute set, but this doesn't require moving python-packages.nix or the other changes made to that file. The Python packages in all-packages.nix should simply be moved to python-packages.nix, and ideally changed to use buildPythonPackage. svn path=/nixpkgs/trunk/; revision=21196
* - adding experimental python31 buildMarc Weber2010-04-17
| | | | | | | | | - cleanup python libraries: * moving all python libraries into a attr set into a directory so that expressions can be used for both: python 2.5 and 2.6 easily * disabling packages which don't build svn path=/nixpkgs/trunk/; revision=21142
* Updating some py-gtk things.Lluís Batlle i Rossell2010-04-06
| | | | | | With a newer glib, I could have used a newer pyobject. svn path=/nixpkgs/trunk/; revision=20962
* add pycairo: cairo bindings for cairoArmijn Hemel2007-05-13
svn path=/nixpkgs/trunk/; revision=8666