First,
http://trac.sagemath.org/sage_trac/ticket/6781
now has a reviewable patch attached to it. This ticket deals with
adding ECL as a library to Python.
Since LISP and Python are actually rather closely related in how they
view data, one can map over
a lot of the data in a rather faithful fash
On Sun, Oct 25, 2009 at 10:45 AM, John Cremona wrote:
>
> Beautiful, thanks. Yes, I do recognise it from Lloyd's book.
Here are some other images by Tom Boothby, by the way:
http://8tb.us/home/boothby/cover/samples/
William
--~--~-~--~~~---~--~~
To post to
On Sun, Oct 25, 2009 at 4:15 PM, Georg S. Weber
wrote:
>
> Sigh.
>
> It seems that in the recent past, I never moved Sage installs after
> building, whenever I wanted to do development. So whenever I created
> clones under devel/, the Sage install in question was still in
> precisely the same pla
We have a Sage server on our campus. We don't have departmental
sysadmins, instead it is maintained by the same folks who do the
administrative systems for the whole campus. I can probably only
reasonably expect two upgrades a year from them, at most. Once in the
summer and maybe over the winte
(warning, blatant patch marketing)
You think this is a shame:
---
Magma:
R:=PolynomialRing(GF(2));
P:=x^257+x^31+x^2+x+1;
time IsPrimitive(P);
true
Time: 0.010
---
Sage:
R.=GF(2)[]
Sigh.
It seems that in the recent past, I never moved Sage installs after
building, whenever I wanted to do development. So whenever I created
clones under devel/, the Sage install in question was still in
precisely the same place (path), where it had been built. This works
fine even with bleedin
> I just tested cloning on a new sage-4.2 build on sage.math (linux) and
> bsd.math (os x) and it worked in both cases.
>
> -- William
>
Hi William,
thanks for your quick support!
Strangely, cloning does not work anymore for me even for Sage-4.1.2
and Sage-4.1.1. At least for Sage-4.1.1, cloni
Hi William!
On 25 Okt., 16:00, William Stein wrote:
[...
> > Is such feature already provided? If not, perhaps the following is
> > doable: spkg-install of some optional package could write its Sage-
> > tree dependencies into a certain file (I think SAGE_ROOT/spkg/
> > installed/ would be a goo
Hello all, I looked at trac 7084 http://trac.sagemath.org/sage_trac/ticket/7084
* If I enter the commands from test section in
sage: var('m')
m
sage: assume(n, 'integer'); assume(m, 'integer')
into Sage session (4.2), then Sage hangs. I have to enter also var
('n') to co
On Sun, Oct 25, 2009 at 1:09 PM, Georg S. Weber
wrote:
>
> Hi all,
>
> on my MacIntel, cloning (i.e. "sage -clone blah") does not seem to
> work anymore. During cloning, several extensions are built anew (that
I just tested cloning on a new sage-4.2 build on sage.math (linux) and
bsd.math (os x)
On Sun, Oct 25, 2009 at 5:15 PM, William Stein wrote:
>
> Hello,
>
> Mike Hansen and I have released sage-4.2.
>
> You can download the source here:
> http://sage.math.washington.edu/sage/src/sage-4.2.tar
> Binaries, official announcements, etc., will follow in a few days.
Binary for sage.math i
Hi all,
on my MacIntel, cloning (i.e. "sage -clone blah") does not seem to
work anymore. During cloning, several extensions are built anew (that
was not always the case, and I do wonder why this was introduced).
Until, and including:
building 'sage.ext.interpreters.wrapper_cdf' extension
everyt
> Here you go:
>
> http://wstein.org/home/wstein/tmp/modform.png
>
Ahh,
a very nice picture indeed! This picture propitiates me quite a bit
with the inclusion of the pil spkg (in its current state) in Sage.
Hmm, the p-adic world is discontinuous, but also might produce nice
pictures similar l
On Sun, Oct 25, 2009 at 1:05 PM, William Stein wrote:
>
> Hi Sage-Devel,
>
...
>
> 5. I try again from scratch with a.thumbnail((int(1000),int(1000)))
> to force plane Python ints. This works:
>
> sage: import Image
> sage: a = Image.open('huge.png')
> sage: time a.thumbnail((int(1000),int(10
Beautiful, thanks. Yes, I do recognise it from Lloyd's book.
John
2009/10/25 William Stein :
>
> On Sun, Oct 25, 2009 at 10:38 AM, John Cremona wrote:
>>
>> Can we see the picture? I have always wanted to know what a modular
>> form looks like ;)
>
> Here you go:
>
> http://wstein.org/home/
On Sun, Oct 25, 2009 at 10:38 AM, John Cremona wrote:
>
> Can we see the picture? I have always wanted to know what a modular
> form looks like ;)
Here you go:
http://wstein.org/home/wstein/tmp/modform.png
It may look familiar from the cover of Lloyd Kilford's book.
I'm not sure which one
Can we see the picture? I have always wanted to know what a modular
form looks like ;)
John
2009/10/25 William Stein :
>
> Hi Sage-Devel,
>
> I have a huge 23MB 1x1 PNG image (that Tom Boothby made a long
> time ago of a modular form), and I want to shrink it. Loading it in
--~--~--
One of the main point I took into account was the necessity of not
adding a significant amount of work to the community, actually.
Basically, my only point was aimed to take advantage of something that
I think we already have, but that we don't value enough right now.
As I see it, I think that it
Hi Sage-Devel,
I have a huge 23MB 1x1 PNG image (that Tom Boothby made a long
time ago of a modular form), and I want to shrink it.Loading it in
GIMP on my mac just freezes GIMP, and similar with other programs. I
don't feel like installing ImageMagick from source right now. So, I
t
On Sun, Oct 25, 2009 at 1:26 AM, Juan Jose Garcia-Ripoll
wrote:
> I got an itanium account recently. I am testing on that right now
> Juanjo
I realized that I also got you an Itanium account on the two Itanium
boxes I test on. However, finger says you haven't logged in, so maybe
you forgot abou
On Sun, Oct 25, 2009 at 5:20 AM, Simon King wrote:
>
> Hi!
>
> IIRC it is encouraged by the developer guide to inherit from Parent,
> Ring, RingElement etc, in order to fit new code cleanly into Sage. But
> then, it would be fair to support that an (optional) spkg c-imports
> those classes. By "s
On Sat, Oct 24, 2009 at 10:17 PM, Robert Bradshaw
wrote:
>
> On Oct 24, 2009, at 7:10 PM, Jason Grout wrote:
>
>> mhampton wrote:
>>
>>> One thing that was mentioned on another thread is that the version
>>> number for sage-4.1.2 was quite misleading. It would help a lot if
>>> the version numbe
>
> Is it not more obvious to call the >=4.2 'beta' versions, if that
> strategy is
> used. Virtually everyone knows a 'beta' version of software is subject
> to bugs.
Well, I don't think 4.1.2 is any more unstable than 4.1.1, but 4.1.1
happens to be the one we have installed. It's very important
great! what is "live doc converter" btw?
On Oct 23, 3:30 pm, Pat LeSmithe wrote:
> On 10/23/2009 05:23 AM, zeliboba wrote:
>
> > I started to play with sage recently and noticed that stand-alone
> > scripts and worksheets are really decoupled. I would prefer to have
> > script, for doing quick a
Hi!
IIRC it is encouraged by the developer guide to inherit from Parent,
Ring, RingElement etc, in order to fit new code cleanly into Sage. But
then, it would be fair to support that an (optional) spkg c-imports
those classes. By "support", I mean that Sage's upgrade script should
do an automatic
As far as I know, that is indeed the problem. Sage's version is linked to
termcap.
I am not sure whether this is the reason, but in /etc/profile, there is a
line that goes:
{{{
unset TERMCAP
}}}
which may be the problem. Also, Arch Linux has no libtermcap.
- Tim Joseph Dumol
On Sun, Oct 25
Pablo Angulo wrote:
> For me, it would be enough if the binaries for the previous versions
> did not disappear from the mirrors, and big changes in SAGE came with
> big changes in the version number. I could then tell my students to:
> "use any version of SAGE starting with 4.1, but use SAGE>=4.
Hi,
the readline issue during build:
symbol lookup error: /opt/sage/local/lib/libreadline.so.6: undefined symbol: PC
is still here (on Arch 64 bit at least), copying native
libreadline.so.6 from Arch to /opt/sage/local/lib solves the issue.
Quick check shows, that readline in sage is not linked
I have found that the GNU C library routines for controlling the
signalling of floating point exceptions, which are not really C
standard but GNU extensions, do not work in the itanium. Well, they
work in the sense that they can suppress the signalling but when
activating it, saving and restoring
For me, it would be enough if the binaries for the previous versions
did not disappear from the mirrors, and big changes in SAGE came with
big changes in the version number. I could then tell my students to:
"use any version of SAGE starting with 4.1, but use SAGE>=4.2 at your
own risk" right at
Hi,
no matter how you name it (I would prefer "LTS", i.e. long term
support), the basic problem is time resp. manpower.
I remember that when Linux switched from versions 2.0.x to 2.2.x, from
2.2.x to 2.4.x, and from 2.4.x to 2.6.x, the then "old" versions 2.0,
2.2, 2.4 had specific maintainers "
I got an itanium account recently. I am testing on that right now
Juanjo
On Sun, Oct 25, 2009 at 5:44 AM, William Stein wrote:
> On Sat, Oct 24, 2009 at 10:49 AM, Robert Dodier
> wrote:
>> On 10/24/09, William Stein wrote:
>>
>>> I can't get Maxima--5.19.1 to build on Itanium on top of ECL.
On Sat, Oct 24, 2009 at 11:56 PM, Ondrej Certik wrote:
>
> On Sat, Oct 24, 2009 at 4:11 PM, William Stein wrote:
>>
>> Hi,
>>
>> I was reading through the Cygwin User's Guide today and decided to try
>> again to try to get Sage to startup on Cygwin. I took my 4.1 build
>> (see http://trac.sagem
33 matches
Mail list logo
