The doctest picks up the pickled stuff from
$SAGE_ROOT/data/extcode/pickle_jar/pickle_jar.tar.bz2
which you get in the source distribution.
Actually, if I try, on ARM, at the sage prompt the following:
sage: sage.structure.sage_object.unpickle_all()
I get the same "Failed to unpickle 5 objects."
Here is an experiment I just tried on ARM:
create linear code from the example in LinearCode? (it's the same as in
pickle_jar.tar.bz2)
Pickle it:
sage: sage.structure.sage_object.picklejar(C,dir='/tmp/jj')
Quit Sage.
Start Sage and unpickle it:
sage: sage.structure.sage_object.unpickle_all('/tmp
On 2012-01-29 04:00, William Stein wrote:
> Pari Days slides!
Some feature which could be useful for Sage in the future: PARI has an
experimental patch changing the format for real numbers to allow a
precision in *bits*. Right now, precision in PARI must be a multiple of
the wordsize (32 or 64).
On Sun, Jan 29, 2012 at 02:53:49AM -0800, Dima Pasechnik wrote:
> Here is an experiment I just tried on ARM:
> create linear code from the example in LinearCode? (it's the same as in
> pickle_jar.tar.bz2)
>
> Pickle it:
> sage: sage.structure.sage_object.picklejar(C,dir='/tmp/jj')
> Quit Sage.
>
Are you saying it's actually a Python bug, not a Sage bug?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-dev
On Sun, Jan 29, 2012 at 03:18:45AM -0800, Dima Pasechnik wrote:
> Are you saying it's actually a Python bug, not a Sage bug?
(Aside: please quote at least part of the message you're replying to.
I'll assume you're asking me...)
No, not python, but the custom reduce/unpickle functions we have for
Le 29/01/2012 12:13, Willem Jan Palenstijn a écrit :
So this is the same issue with char being unsigned on your platform.
Specifically, it seems the corresponding __reduce__ function converts a char
array into a list of python ints, which has range 0-255 for you, instead of the
-128-127 on x86. A
On Sat, Jan 28, 2012 at 04:36:17PM +0100, Julien Puydt wrote:
> Le 29/01/2012 12:13, Willem Jan Palenstijn a écrit :
> >So this is the same issue with char being unsigned on your platform.
> >Specifically, it seems the corresponding __reduce__ function converts a char
> >array into a list of python
On Sunday, 29 January 2012 20:05:26 UTC+8, Willem Jan Palenstijn wrote:
>
> On Sat, Jan 28, 2012 at 04:36:17PM +0100, Julien Puydt wrote:
> > Le 29/01/2012 12:13, Willem Jan Palenstijn a �crit :
> > >So this is the same issue with char being unsigned on your platform.
> > >Specifically, it seem
Le 29/01/2012 13:38, Dima Pasechnik a écrit :
and then it does (line 1750):
cdef char *buf = gdImagePngPtr(im, &size)
data = [buf[i] for i in range(size)]
and this data goes into the pickle. No wonder it gets different on
different platforms!
Would that also be a case of just using uint8_t an
On Sunday 29 January 2012, Dima Pasechnik wrote:
> On Sunday, 29 January 2012 20:05:26 UTC+8, Willem Jan Palenstijn wrote:
> > On Sat, Jan 28, 2012 at 04:36:17PM +0100, Julien Puydt wrote:
> > > Le 29/01/2012 12:13, Willem Jan Palenstijn a �crit :
> > > >So this is the same issue with char being
On Sunday, 29 January 2012 00:34:28 UTC+8, Snark wrote:
>
> Le 29/01/2012 13:38, Dima Pasechnik a �crit :
> > and then it does (line 1750):
> >
> > cdef char *buf = gdImagePngPtr(im, &size)
> > data = [buf[i] for i in range(size)]
> >
> > and this data goes into the pickle. No wonder it gets di
Hi all,
I am focusing on the LLL algorithm for my PhD.
Specifically, on its application on Factorising RSA modulus N with
high or low-order bits (of the prime p) known.
My scope is to use an implementation and run tests on the
factorisation problem.
SAGE has embedded Stehle's LLL version: the fpl
On Jan 25, 2012, at 2:52 PM, kcrisman wrote:
> Ivan's iPhone app is cool. However, when it links to sagenb or
> sagemath.org, it looks ... unhelpful. Perhaps this is possible to fix
> easily - exchange below. Is there someone for whom this would be only
> epsilon/two of effort to fix, who has
Le 29/01/2012 13:54, Dima Pasechnik a écrit :
On Sunday, 29 January 2012 00:34:28 UTC+8, Snark wrote:
Le 29/01/2012 13:38, Dima Pasechnik a �crit :
> and then it does (line 1750):
>
> cdef char *buf = gdImagePngPtr(im, &size)
> data = [buf[i] for i in range(size)]
William,
I guess I would like to know which of the problems you refer to still
are a problem in the updates to Jmol that are awaiting review?
The things left that I know about are:
1) The way Jmol functions in interacts is a problem, but this has
nothing to do with Jmol. It is the way the intera
On Sun, Jan 29, 2012 at 13:55, R. Andrew Ohana wrote:
> On Sat, Jan 28, 2012 at 21:19, David Roe wrote:
>> * I would like to still allow "sage -t" as a way to access the "sage
>> test" subcommand, "sage -b" to access the "sage build" subcommand,
>> etc.
> This is fairly straightforward with the a
I couldn't spot the version in the app, but the Android market told me
there was an update and this immediately told me it contained the web
page not available fix. It also contained new examples. Very
pleasingly, they all appeared to work, including the sliders, and the
plots.
Marvellous!! And th
> On Jan 28, 8:48 pm, Volker Braun wrote:
> Just do double check, you have v0.2? (Menu->Changelog)
The update fixed the page not available problem for me.
Also, this app is really awesome.
A couple of (minor) things I've noticed with what's been
implemented so far:
* Changing screen orientation
Well, I wonder if we shouldn't ask around a bit more. If a day later you
found something better than pre3d, maybe soon you will find something even
better than three.js? :P As to who would be a good community to ask about
this stuff, though, I have no idea.
-Keshav
Join us in #sagemath on
On Sunday, January 29, 2012 4:54:58 AM UTC-8, Dima Pasechnik wrote:
>
> Cause int8_t would retain the compatibility with the existing pickles
> created on x86.
> I guess we should write a sage-devel post asking people to look at other
> cases of this they are aware about
>
+1
>
--
To post
Hi,
My cython patch "readline_extra_commands" works well on Mac but fails on
Ubuntu at runtime with the following message:
ImportError: ../sage/misc/readline_extra_commands.so: undefined symbol:
rl_last_func
So the linker do not find the symbol in the readline library linked to
Python. What i
On Jan 29, 2012, at 7:57 PM, Keshav Kini wrote:
>>> I think the key change should be to become Posix compliant, and
>>> these are allowable short options. And they combine nicely: "sage
>>> -bta" would mean rebuild everything and test everything.
>> These commands are odd. For most programs you
On Sunday 29 January 2012, Ermis wrote:
> Hi all,
Hi,
> I am focusing on the LLL algorithm for my PhD.
> Specifically, on its application on Factorising RSA modulus N with
> high or low-order bits (of the prime p) known.
> My scope is to use an implementation and run tests on the
> factorisation
Are you linking with -lreadline? Whats the entry in module_list.py
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group
On Mon, Jan 30, 2012 at 04:36, Ivan Andrus wrote:
> I agree it's ugly. I think what the user really wants is things like
>
> sage test --build-first
>
> rather than
>
> sage build test
>
> I can't imagine any ever wanting
>
> sage build shell test notebook
>
> In other words, the test command wou
On Mon, Jan 30, 2012 at 05:27, Keshav Kini wrote:
> Hmm. Indeed, `sage -sh -c gap -b` still displays a banner, for
> example, whereas `sage -gap -b` does not. `sage -sh -c gap -- -b`
> doesn't work either. `sage -sh -c 'gap -b'` does, though, so that's a
> workaround. The question then becomes, wo
There's an LLL in flint 1.5, called ULLL which is very fast for large
lattice entries. It is probably subquadratic with respect to bit size
of the entries though likely not quasilinear. (We also have a highly
hacked version of fpLLL in flint specifically set up for knapsack
lattices.)
I recently b
On 2012-01-29 22:29, Keshav Kini wrote:
> On Mon, Jan 30, 2012 at 05:27, Keshav Kini wrote:
>> Hmm. Indeed, `sage -sh -c gap -b` still displays a banner, for
>> example, whereas `sage -gap -b` does not. `sage -sh -c gap -- -b`
>> doesn't work either. `sage -sh -c 'gap -b'` does, though, so that's
It is
Extension('sage.misc.readline_extra_commands',
sources = ['sage/misc/readline_extra_commands.pyx']),
Do I need to add "-lreadline" somewhere here?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an em
On Monday, 30 January 2012 03:49:45 UTC+8, Keshav Kini wrote:
>
> Well, I wonder if we shouldn't ask around a bit more. If a day later you
> found something better than pre3d, maybe soon you will find something even
> better than three.js? :P As to who would be a good community to ask about
>
Yes you need at least libraries = ['readline']. If you need other libraries
they must be declared as well.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit t
I wonder why that was not necessary for Mac. Anyway, thank you very much!
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.
Working on the ARM port (kudos to Snark), which has, unlike x86, unsigned
char, we stumbled upon several places in Sage library (in Cython code)
where char type was used for (essentially) operating on bit strings.
One example (in Sage 4.8) is computing pickle for a dense Z_2-matrix in
matrix/Ma
Because OSX uses the old ld behavior of implicitly guessing DSOs. For
various reasons this is a bad idea and has been turned off on linux
distributions in the last couple of years.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an ema
Le 30/01/2012 03:10, Dima Pasechnik a écrit :
Working on the ARM port (kudos to Snark), which has, unlike x86,
unsigned char, we stumbled upon several places in Sage library (in
Cython code) where char type was used for (essentially) operating on bit
strings.
To be more specific : all platforms
36 matches
Mail list logo
