By the way, this page:
http://www.sagemath.org/doc/tutorial/afterword.html#the-pre-parser-differences-between-sage-and-python
from the tutorial is also relevant.
John
On Monday, May 26, 2014 6:04:04 PM UTC-7, robin wrote:
>
> brilliant, thanks Leif.
>
> It'd be nice to have an explicit "
brilliant, thanks Leif.
It'd be nice to have an explicit "Note: " on the documentation for load()
which states this extension-dependent behaviour for newbies like me. In my
world (mostly R) the file extension is immaterial, and I'm sure this issue
is a gotcha for many people like me.
best wi
robin wrote:
> Can anyone advise? I am very very very reluctant to
> adopt the ghastly "**" notation.
If you want your file to get preparsed (such that the Sage preparser
replaces '^' by '**' "internally" when you load or run the file with
'sage'), simply rename your file
> > Can anyone advise? I am very very very reluctant to
> > adopt the ghastly "**" notation.
>
> If you want your file to get preparsed (such that the Sage preparser
> replaces '^' by '**' "internally" when you load or run the file with
> 'sage'), simply rename your file to "f.sage".
>
> Si
robin hankin wrote:
Hi, debian linux, Sage-6.2.
It took me some time to track down a problem in my code that boiled
down to the interpretation of a caret ("^") in a file which was read
using load() in a sage session.
Specifically, I have a file called "f.py" which contains a single line,
"o =
Hi, debian linux, Sage-6.2.
It took me some time to track down a problem in my code that boiled down
to the interpretation of a caret ("^") in a file which was read using
load() in a sage session.
Specifically, I have a file called "f.py" which contains a single line, "o
= 10^6". I load() this
the fpLLL docs state that CVP support is experimental and shouldn't be used
yet. If your CVP instance is BDD (i.e. you know a bound) you could reduce it
to uSVP e.g. like this: http://eprint.iacr.org/2013/602.pdf
On Monday 26 May 2014 12:45:55 J.A. Ketch wrote:
> for CVP the only function is L.c
for CVP the only function is L.closest_vector(t) which uses
Miccianchio-Voulgaris algorithm. Is there also another algorithm from
fplll?
thanks
On Tuesday, May 13, 2014 8:37:25 PM UTC+3, Martin Albrecht wrote:
>
> On Tuesday 13 May 2014 09:51:27 J.A. Ketch wrote:
> > are the following algorith
On Sun, 25 May 2014, Gabriel Furstenheim Milerud wrote:
There is a memory leak in the evaluation of multivariable polynomials:
I wrote about same problem on sage-devel at 2014-05-08.
-C.=GF(2)[]
My example did not use GF, just QQ.
--
Jori Mäntysalo
--
You received this message because yo
