about summary refs log tree commit diff
path: root/pkgs/development/python-modules/cypari2
diff options
context:
space:
mode:
authorTimo Kaufmann <timokau@zoho.com>2018-12-20 23:51:48 +0100
committerGitHub <noreply@github.com>2018-12-20 23:51:48 +0100
commit64b9df085d90078f2db958bf413cc3df4e224629 (patch)
treea7fa8b8b2101ba8f9b60774165eadfd91adc0160 /pkgs/development/python-modules/cypari2
parent0aac84e1c30000b3706c186d8a22662cb1825d3d (diff)
Revert "python: cypari2: 1.3.1 -> 2.0.0" (#52596)
This reverts commit 7c9ca654801d472563ddac4bf488ebdabc2bb491. The
cypari2 update is not ready. The package is pretty much only used for
sage and the update causes problems:
https://trac.sagemath.org/ticket/26442#comment:33
I've already reverted this once before.
Diffstat (limited to 'pkgs/development/python-modules/cypari2')
-rw-r--r--pkgs/development/python-modules/cypari2/default.nix4
1 files changed, 2 insertions, 2 deletions
diff --git a/pkgs/development/python-modules/cypari2/default.nix b/pkgs/development/python-modules/cypari2/default.nix
index 9a9be578ca8c1..a77e98dae4c88 100644
--- a/pkgs/development/python-modules/cypari2/default.nix
+++ b/pkgs/development/python-modules/cypari2/default.nix
@@ -12,11 +12,11 @@
 buildPythonPackage rec {
   pname = "cypari2";
   # upgrade may break sage, please test the sage build or ping @timokau on upgrade
-  version = "2.0.1";
+  version = "1.3.1";
 
   src = fetchPypi {
     inherit pname version;
-    sha256 = "32fad615d773e9b5a9394c078ddc2c868e64e35f1ac9633ff90b456901b9d886";
+    sha256 = "04f00xp8aaz37v00iqg1mv5wjq00a5qhk8cqa93s13009s9x984r";
   };
 
   # This differs slightly from the default python installPhase in that it pip-installs