#8345: cannot convert symbolic functions back from maxima
-----------------------------------+----------------------------------------
   Reporter:  burcin               |          Owner:  was            
       Type:  defect               |         Status:  positive_review
   Priority:  major                |      Milestone:  sage-4.7.1     
  Component:  interfaces           |       Keywords:                 
Work_issues:                       |       Upstream:  N/A            
   Reviewer:  Karl-Dieter Crisman  |         Author:  Burcin Erocal  
     Merged:                       |   Dependencies:                 
-----------------------------------+----------------------------------------
Changes (by kcrisman):

  * status:  needs_review => positive_review


Old description:

> From sage-devel:
>
> {{{
> On Mon, 22 Feb 2010 07:02:21 -0800 (PST)
> Håkan Granath <[email protected]> wrote:
>
> > Typesetting conjugates of variables (that has been passed to
> > Maxima and back?) is strange. In e.g. Sage 4.2 this did not
> > happen.
> >
> > ----------------------------------------------------------------------
> > | Sage Version 4.3.3, Release Date: 2010-02-21                       |
> > | Type notebook() for the GUI, and license() for information.        |
> > ----------------------------------------------------------------------
> > sage: assume(x,'complex')
> > sage: latex(x.conjugate())
> > \overline{x}
> > sage: latex(x.conjugate().factor())
> > {\rm conjugate}\left(x\right)
> }}}
>
> Somehow we don't recognize the conjugate function in the string we get
> back from maxima, and create a new one. The last line above is the
> default latex typesetting for symbolic functions.
>

> The thread is here:
>
> http://groups.google.com/group/sage-devel/t/cd43a14bee6e9be

New description:

 From sage-devel:

 {{{
 On Mon, 22 Feb 2010 07:02:21 -0800 (PST)
 Håkan Granath <[email protected]> wrote:

 > Typesetting conjugates of variables (that has been passed to
 > Maxima and back?) is strange. In e.g. Sage 4.2 this did not
 > happen.
 >
 > ----------------------------------------------------------------------
 > | Sage Version 4.3.3, Release Date: 2010-02-21                       |
 > | Type notebook() for the GUI, and license() for information.        |
 > ----------------------------------------------------------------------
 > sage: assume(x,'complex')
 > sage: latex(x.conjugate())
 > \overline{x}
 > sage: latex(x.conjugate().factor())
 > {\rm conjugate}\left(x\right)
 }}}

 Somehow we don't recognize the conjugate function in the string we get
 back from maxima, and create a new one. The last line above is the default
 latex typesetting for symbolic functions.


 The thread is here:

 http://groups.google.com/group/sage-devel/t/cd43a14bee6e9be

 ----
 Apply [attachment:trac_8345-doctest.patch].

--

Comment:

 Okay, thanks - and thanks for the tip, in the last few months I've finally
 started using queues.

 I already tried several things yesterday, so all is well.  Positive
 review.

 Incidentally, this has been fixed for a ''while'':
 {{{
 ----------------------------------------------------------------------
 | Sage Version 4.4.4, Release Date: 2010-06-23                       |
 | Type notebook() for the GUI, and license() for information.        |
 ----------------------------------------------------------------------
 Loading Sage library. Current Mercurial branch is: hackbranch
 sage: assume(x,'complex')
 sage: latex(x.conjugate().simplify())
 \overline{x}
 sage:
 }}}

 ----
 Apply [attachment:trac_8345-doctest.patch].

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8345#comment:5>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to