Changes between Version 2 and Version 4 of Ticket #13290


Ignore:
Timestamp:
07/27/12 11:56:23 (10 years ago)
Author:
jdemeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13290

    • Property Status changed from new to needs_review

  • Ticket #13290 – Description

    v2 v4  
    11Currently, Sage uses a development version of MPC (stable 0.9 had build issues on certain platforms).
    22
    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.
     3We 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.
    64
    75'''spkg''': [http://boxen.math.washington.edu/home/jdemeyer/spkg/mpc-1.0.spkg]
    86
    97'''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.