Changes between Version 1 and Version 7 of Ticket #16732


Ignore:
Timestamp:
07/30/14 15:53:22 (5 years ago)
Author:
nbruin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16732

    • Property Status changed from new to needs_review
    • Property Cc kcrisman burcin added
    • Property Summary changed from Fix translation of psi(x,y) to/from maxima to Fix _maxima_init_evaled_ use, as well as translations of psi etc. to/from maxima.
    • Property Priority changed from minor to major
    • Property Branch changed from to u/nbruin/ticket/16732
    • Property Commit changed from to c28d9bdcb7ed0023f5eccb31d021207668259ee2
  • Ticket #16732 – Description

    v1 v7  
    2020li[3](x)
    2121}}}
    22 As you see, the polylog doesn't get translated properly! This indicates misimplemented `_maxima_init_evaled_`, and probably those occur in several spots. Perhaps the way `_maxima_init_evaled_` gets called by the translator needs amendment? (the arguments need processing). The problem seems to occur in [http://git.sagemath.org/sage.git/tree/src/sage/functions/special.py#n502 sage/functions/special.py line 502], where the arguments are apparently fed raw into `_maxima_init_evaled_` and where `_maxima_init_evaled_` is usually implemented as some basic string manipulation.
     22As you see, the polylog doesn't get translated properly! This indicates misimplemented `_maxima_init_evaled_`, and probably those occur in several spots. Perhaps the way `_maxima_init_evaled_` gets called by the translator needs amendment? (the arguments need processing). The problem seems to occur in [http://git.sagemath.org/sage.git/tree/src/sage/symbolic/expression_conversions.py#n550 sage/symbolic/expression_conversion line 550], where the arguments are fed raw into `_maxima_init_evaled_` (compare it to the cases below where the operands do get passed through the interface) and where `_maxima_init_evaled_` is usually implemented as some basic string manipulation.
    2323
    2424