Changes between Version 2 and Version 4 of Ticket #13290
- Timestamp:
- 07/27/12 11:56:23 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13290
-
Property
Status
changed from
new
toneeds_review
-
Property
Status
changed from
-
Ticket #13290 – Description
v2 v4 1 1 Currently, Sage uses a development version of MPC (stable 0.9 had build issues on certain platforms). 2 2 3 Upgrade to the just-released MPC-1.0: [http://www.multiprecision.org/index.php?prog=mpc] 4 5 At the same time, why not import `MPComplexField` by default and add MPC to the reference manual. 3 We should upgrade to the just-released MPC-1.0: [http://www.multiprecision.org/index.php?prog=mpc]. While we're at it, import `MPComplexField` by default and add MPC to the reference manual. 6 4 7 5 '''spkg''': [http://boxen.math.washington.edu/home/jdemeyer/spkg/mpc-1.0.spkg] 8 6 9 7 '''apply''' [attachment:13290_mpc_1_0.patch] to the Sage library. 8 9 === mpc-1.0 (Jeroen Demeyer, 27 July 2012) === 10 * Trac #13290: upgrade to stable version 1.0. 11 * Remove no_fortify_source.patch (which is upstream now). 12 * Remove legacy "unset RM" command.