On Fri, Aug 30, 2013 at 1:35 PM, David Joyner wrote:
> On Fri, Aug 30, 2013 at 2:44 PM, William Stein wrote:
>> On Fri, Aug 30, 2013 at 11:07 AM, XXX wrote:
>>> Hi William,
>>>
>>> I know you have had a long and interesting "history" with Magma.
>>>
>>> You're probably already aware of this but i
On Fri, Aug 30, 2013 at 2:44 PM, William Stein wrote:
> On Fri, Aug 30, 2013 at 11:07 AM, XXX wrote:
>> Hi William,
>>
>> I know you have had a long and interesting "history" with Magma.
>>
>> You're probably already aware of this but if you're not, apparently the
>> Simons Foundation is now fundi
2013/8/30, William Stein :
> On Fri, Aug 30, 2013 at 11:07 AM, XXX wrote:
>> Hi William,
>>
>> I know you have had a long and interesting "history" with Magma.
>>
>> You're probably already aware of this but if you're not, apparently the
>> Simons Foundation is now funding the distribution of Magma
I wrote StdOutContext for use cases like this actually. Particularly, to
capture the protocol of a GB computation:
in sage.rings.polynomial.multi_polynomial_ideal:
from sage.interfaces.magma import MagmaGBLogPrettyPrinter
if prot:
log_parser = MagmaGBLogPrettyPrinter(verbo
On Wed, Dec 14, 2011 at 4:13 PM, David Roe wrote:
> I helping a colleague try to wrap some magma code that uses verbose
> print statements. Apparently, just setting the verbose flag is not
> enough:
>
> sage: magma.SetVerbose("Factorization",1)
> sage: magma.Factorization(56654654654464)
> [ <2,
There's a ticket fixing this at #7870, merged in 4.7.alpha4.
Which version were you using?
On your last point: not enough!
John
On Tue, Apr 19, 2011 at 2:44 PM, Marco Streng wrote:
> Hi all,
>
> Is it just me, or is magma(K) broken for number fields K?
>
> The following example is in number_f
