Changes between Version 5 and Version 7 of Ticket #17505


Ignore:
Timestamp:
05/05/17 07:19:25 (5 years ago)
Author:
rws
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17505

    • Property Milestone changed from sage-wishlist to sage-8.0
  • Ticket #17505 – Description

    v5 v7  
    2626NameError: name 'product' is not defined
    2727}}}
    28 * Creatnig it it by casting a Maxima expression via the library interface gives nonsense :
    29 {{{
    30 sage: X(j).maxima_methods().prod(j,1,p)
    31 X(j)^p
    32 sage: X(j).maxima_methods().product(j,1,p)
    33 X(j)^p
    34 }}}
    35 (Note : similar nonsense also happens with sums :
    36 {{{
    37 sage: X(j).maxima_methods().sum(j,1,p)
    38 p*X(j)
    39 }}}
    40 )
    41 * But something (what ?) can be created via the Maxima {{{pexpect}}} interface :
     28
     29At the moment anonymous functions named `product` can be created via the Maxima {{{pexpect}}} interface and they even behave as products in specific cases:
    4230{{{
    4331sage: maxima("prod(X(j),j,1,p)").sage().log().log_expand()
     
    4533}}}
    4634
    47 The part of the problem bound to the Maxima library interface is the object of #22920. The present ticket aims at creating a Sage function/method correctly creating a symbolic product object.
     35The present ticket aims at creating a Sage function/method either evaluating the sum, or correctly creating a unevaluted symbolic product object.
    4836
    49 The ticket would have to decide which of (Maxima,SymPy) would be used as default for this.
     37For evaluation the ticket would have to decide which of (Maxima,SymPy) would be used as default for this.
    5038{{{
    5139sage: import sympy
     
    5846}}}
    5947
    60 Any Maxima implementation likely depends on #17502.
     48Creating products by casting a Maxima expression via the library interface gives nonsense, see #17502.