Hi,
nice to have a new release!
I tried to build but didn't get far, GCC 4.4 here (actually gcc
version 4.4.0 20090526 prerelease that fixes other problem with build
I had with sage 4.0). Anyway - had to patch libsingular (it use
deprecated strchr form in 2 places, simple cast is enough to fix i
> That did the trick -- ran fine and no "failure" line at the end. (I
> moved that line to the end as suggested)
>
Interesting ... that means that the call to sys.exit(0) is generating
an exception that's getting caught in the except: clause. Can you file
a ticket for this? I'll happily review i
It's a small point but the title of
#6193: John Cremona: implement elliptic logarithm
is nto really accurate since we already had the elliptic log, but the
implementation has been improved. Therefore it's not exactly a "new
feature". (there will be a related new feature soon, namely
"implement c
Dr. David Kirkby wrote:
> In the process of building Sage on t2, I noticed another failure, which
> I'm somewhat surprised has not been seen on all platforms. I've
> submitted this as ticket 6278, where more information is provided than
> here.
>
> Essentially the following packages are now in
2009/6/19 Craig Citro :
>
>> All seemed well with that test (all etsts passed, etc), but the final
>> lines of output are
>>
>> All tests passed! Popping patches from queue ...
>> cd "/home/jec/sage-4.0.2/devel/sage" && hg qpop -a
>> cd "/home/jec/sage-4.0.2/devel/sage" && hg qdelete trac_5307.pat
2009/6/19 Craig Citro :
>
>>> Similar error with any other sage -merge command. Am I doing
>>> something wrong?
>>
>> I think I had this problem based on the current directory. Could you
>> try in a different directory? (I think this is a sage-wide problem
>> but I can't say with certainty.)
>>
I'm the release manager for sage-4.0.3. I'll attempt to upgrade
Python to 2.6, and if I succeed, I'll rename the release to sage-4.1.
In about an hour, I'm going to send out review requests. If you can't
review, please pass the requests along to somebody qualified, or
bounce them back to me as s
Hi folks,
Here is a release note for Sage 4.0.2. I'm sending this only to
sage-release and sage-devel. The announcement on sage-announce will be
forthcoming when binaries are in order, and a release tour is ready.
Sage 4.0.2 was released on June 18th, 2009. It is available at
http://
>> Similar error with any other sage -merge command. Am I doing
>> something wrong?
>
> I think I had this problem based on the current directory. Could you
> try in a different directory? (I think this is a sage-wide problem
> but I can't say with certainty.)
>
Yep, I remember Nick saying som
> All seemed well with that test (all etsts passed, etc), but the final
> lines of output are
>
> All tests passed! Popping patches from queue ...
> cd "/home/jec/sage-4.0.2/devel/sage" && hg qpop -a
> cd "/home/jec/sage-4.0.2/devel/sage" && hg qdelete trac_5307.patch
> Building failed with System
Dear Sage-devel,
There is a file sage/plot/texture.py, and there is a file sage/plot/
plot3d/texture.py. It appears that the plot3d version is a much
improved (e.g. supporting jmol, doctested) version of the other one,
and the only places I could find either one referred to, the import
statement
On Fri, Jun 19, 2009 at 4:23 PM, Bill Page wrote:
>
> -- Forwarded message --
> From: Adam Webb
> Date: Fri, Jun 19, 2009 at 5:55 AM
> Subject: fricas-1.0.6.p0.spkg
> To: bill.p...@newsynthesis.org
>
>
>
> Hi Bill,
>
> I threw together a Sage package. (fricas-1.0.6.p0.spkg,
> http
2009/6/19 Nick Alexander :
>
>> I wanted to try out this feature. Here is what happened. I built
>> 4.0.2.rc3 from scratch, made a clone called test, cd'd into
>> devel/sage-test, initialised MQ by "sage -hg qinit". And then:
>>
>> j...@host-57-89%sage -merge -c
>> Traceback (most recent call l
> I wanted to try out this feature. Here is what happened. I built
> 4.0.2.rc3 from scratch, made a clone called test, cd'd into
> devel/sage-test, initialised MQ by "sage -hg qinit". And then:
>
> j...@host-57-89%sage -merge -c
> Traceback (most recent call last):
> File "/home/jec/sage-curre
SSSE3 is only available on Intel machines and the VIA Nano, so I don't
think that is what you mean.
I'm sure we can get fairly robust binaries which don't make
assumptions about SSE availability, without too much difficulty.
It would help a lot if anyone did have problems with the last Sage x86
It makes sense to me to post to the email lists. I never accomplish
much my private emails...
The test
sage: a = fricas(x+2)
is correctly written as it stands. Sage is supposed to be able to
convert (most) Sage symbolic expressions directly to Axiom/FriCAS
syntax.
Using
sage:a = fricas('x+2')
-- Forwarded message --
From: Adam Webb
Date: Fri, Jun 19, 2009 at 5:55 AM
Subject: fricas-1.0.6.p0.spkg
To: bill.p...@newsynthesis.org
Hi Bill,
I threw together a Sage package. (fricas-1.0.6.p0.spkg,
http://www.mediafire.com/file/whwmdzfimg2) The big change is that the
new ve
William Stein wrote:
> rm -f libbz2.a
> ar cq libbz2.a blocksort.o huffman.o crctable.o randtable.o compress.o
> decompress.o bzlib.o
> make[2]: ar: Command not found
> make[2]: *** [libbz2.a] Error 127
> make[2]: Leaving directory `/home/wstein/t2/sage-4.0.2/spkg/build/bzip2-1.0.5'
> Error build
On Fri, Jun 19, 2009 at 9:06 AM, Dr. David
Kirkby wrote:
>
> Dr. David Kirkby wrote:
>> I have not developed and tested a patch which allows ATLAS to build on
>> Solaris using gcc-4.4.0 on 't2'. Could someone please review please the
>> patch
>>
>> http://trac.sagemath.org/sage_trac/ticket/6276
>
2009/6/18 Craig Citro :
>
> Hi all,
>
> Here's rc3, which *should* be the last rc for this release cycle. I've
> tested it on my laptop and the build farm, and I've had no troubles at
> all, and it's currently going on a few other machines, so hopefully
> that'll turn out fine, too. Please test it
Hello,
Sage-4.0.2 has been released by Craig Citro and Nick Alexander! The
source code is available here:
http://sagemath.org/src/sage-4.0.2.tar
Binaries (only for modern hardware with ssse3) will be available in a
few days (at most), along with a release
tour, release notes, etc. Brave
On Fri, Jun 19, 2009 at 1:13 PM, gsw wrote:
>
>
>
> On 19 Jun., 08:50, Craig Citro wrote:
>> > Yes, the parallel build code was reworked for 4.0.1. Not sure why
>> > we're seeing this, but still.
>>
>> Well, the parallel build code in 4.0.1 *should* be contained to the
>> sage build itself (it'
On 19 Jun., 08:50, Craig Citro wrote:
> > Yes, the parallel build code was reworked for 4.0.1. Not sure why
> > we're seeing this, but still.
>
> Well, the parallel build code in 4.0.1 *should* be contained to the
> sage build itself (it's in sage's setup.py, and it's a separate
> builder that
On Fri, Jun 19, 2009 at 11:58 AM, wrote:
> Hi William,
>
> I'd be happy to have a look at referee this. Do I need to apply
> the dozen or so patches, or what is required? The challenge for
> the referee seems to be to sort out what has been refereed, what
> needs careful inspection.
I don't kn
2009/6/19 Craig Citro :
>
>> My most important debugging tool is logical deduction using my brain.
>>
>
> Someone want to open a trac ticket for including that in Sage? ;)
Not me -- reviewing might be fun but it would never be "closed", would it?
John
>
> -cc
>
> >
>
--~--~-~--~~--
Dr. David Kirkby wrote:
> I have not developed and tested a patch which allows ATLAS to build on
> Solaris using gcc-4.4.0 on 't2'. Could someone please review please the
> patch
>
> http://trac.sagemath.org/sage_trac/ticket/6276
Oops, that was supposed to be 'I have NOW developed a patch !!!
26 matches
Mail list logo
