#5923: [with patch, needs review] Handling of magma and pari input in 
ModularForms
---------------------------+------------------------------------------------
 Reporter:  ljpk           |       Owner:  davidloeffler
     Type:  defect         |      Status:  assigned     
 Priority:  minor          |   Milestone:  sage-4.0     
Component:  modular forms  |    Keywords:               
---------------------------+------------------------------------------------
Description changed by craigcitro:

Old description:

> The ModularForms command has some slightly counter-intuitive behaviour on
> some types of input:
>
> {{{sage: ModularForms(gp(1),12)
> ---------------------------------------------------------------------------
> TypeError
>
> [much snipped error message]
>
> TypeError: Error executing code in GP/PARI:
> CODE:
>         sage[4]=level(sage[3]);
> GP/PARI ERROR:
>   ***   expected character: ',' instead of: sage[4]=level(sage[3]);
>                                                               ^-----
> }}}
>
> I realize that this is because the first element is supposed to be a
> group, although a (Sage) integer is allowed.
>
> Would there be any support for having an if statement in the function to
> catch magma or pari elements and transform them into their Sage
> equivalents?

New description:

 The `ModularForms` command has some slightly counter-intuitive behaviour
 on some types of input:

 {{{
 sage: ModularForms(gp(1),12)
 ---------------------------------------------------------------------------
 TypeError

 [much snipped error message]

 TypeError: Error executing code in GP/PARI:
 CODE:
         sage[4]=level(sage[3]);
 GP/PARI ERROR:
   ***   expected character: ',' instead of: sage[4]=level(sage[3]);
                                                               ^-----
 }}}

 I realize that this is because the first element is supposed to be a
 group, although a (Sage) integer is allowed.

 Would there be any support for having an if statement in the function to
 catch magma or pari elements and transform them into their Sage
 equivalents?

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5923#comment:3>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel

--~--~---------~--~----~------------~-------~--~----~
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