On Thu, Dec 18, 2008 at 3:52 AM, Dan Drake wrote:
> Hello all,
>
> The SageTeX package needs two basic pieces to work: a pure Python
> module, and a pure LaTeX style file. Since a Sage installation is
> necessary for either of those pieces to be useful, it seems like it
> would be wise to include
Hi,
no need to send me any logs since I can reproduce this now. The
problem is that bash as well as sh on OpenSUSE are dynamically linked
against readline, so one we source local/bin/sage-env from an spkg
during build and we do have a compiled and installed libreadline.so
things blow up with a mi
> eisenstein_submodule, sorry I wasn't more specific.
>
Hmm, interesting. Do you have the log? I'm just surprised that
anything could cause that file to timeout, especially without causing
anything else to timeout. Could I con you into running that test
again, and seeing if it still times out? If
eisenstein_submodule, sorry I wasn't more specific.
-Marshall
On Dec 19, 1:00 pm, "Craig Citro" wrote:
> > My ppc powerbook is still slaving away on tests, its almost done and
> > so far just has timeout failures on eisenstein and calculus.py.
>
> What file was the eisenstein timeout on?
>
> -c
On Dec 19, 12:56 pm, henrik22 wrote:
Hi,
> Thank you for the hint. In fact, compilation continues if I
> remove the just created readline from sage-3.2.2/local/lib, so that
> the pari compilation
> is forced to use the version 5.2 already on my computer (/lib64/
> libreadline.so.5.2,
> includ
Thank you for the hint. In fact, compilation continues if I
remove the just created readline from sage-3.2.2/local/lib, so that
the pari compilation
is forced to use the version 5.2 already on my computer (/lib64/
libreadline.so.5.2,
including header files in /usr/include/readline).
Where may I p
On Dec 19, 2008, at 11:56 , Gary Furnish wrote:
>
> Was that with a parallel test? I'm aware of the marker issue but
> haven't been able to consistently reproduce it. The marker was a
> temporary fix to solve even worse race conditions, so its still a step
> in the right direction.
I ran
$ "
Was that with a parallel test? I'm aware of the marker issue but
haven't been able to consistently reproduce it. The marker was a
temporary fix to solve even worse race conditions, so its still a step
in the right direction.
On Fri, Dec 19, 2008 at 12:51 PM, mabshoff wrote:
>
>
>
> On Dec 19,
On Dec 19, 11:45 am, "Justin C. Walker" wrote:
> On Dec 18, 2008, at 23:23 , mabshoff wrote:
Hi Justin,
> Upgraded rc1 to "final" on Mac OS X, both 10.5.5 and 10.4.11, without
> problems.
Well, it was two tiny patches :)
> All tests passed on 10.5.5, but on 10.4.11, I see one failure:
>
On Dec 18, 2008, at 23:23 , mabshoff wrote:
>
> Hi,
>
> Sage 3.2.2 is out and the final sources are at
>
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.2/sage-3.2.2.tar
>
> You can also upgrade by running
>
> ./sage -upgrade
> http://sage.math.washington.edu/home/mabshof
Did you test for the sql alchemy bottleneck without using dsage?
There were some pretty severe (at times) speed issues fixed with dsage
in 3.2.2.
On Fri, Dec 19, 2008 at 11:24 AM, Jason Grout
wrote:
>
> Dan wrote:
>> Thanks for directing me.
>>
>> The bottleneck appears to be queries to a MySQL
> My ppc powerbook is still slaving away on tests, its almost done and
> so far just has timeout failures on eisenstein and calculus.py.
>
What file was the eisenstein timeout on?
-cc
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegro
I found this blog posting:
http://ejohn.org/blog/fireunit/
about
http://fireunit.org/
It's a testing framework for javascript, for the firebug extension in
firefox. It says it is in a very early stage, but probably interesting
for the notebook javascript code - especially because you can simulate
On Dec 18, 10:07 pm, "Craig Citro" wrote:
> > How do I set an environment variable in the Sage code?
>
> From the command line, you can just do:
>
> sage: import os
>
> Then os.environ is a dictionary storing your environment variables. In
> particular:
>
> sage: os.environ['SAGE_BANNER'] = 'no'
henrik22 wrote:
> Hi,
Hi Henrik,
> on Suse 11.1 with gcc 4.3.2 installation stops early in pari-2.3.3.p0
> with
>
>/bin/sh: symbol lookup error: /home/henrik/Pakete/sage-3.2.1/local/
> lib/libreadline.so.5: undefined symbol: PC
>
> I am running on an x64_64 dual core notebook with Suse 11.
Dan wrote:
> Thanks for directing me.
>
> The bottleneck appears to be queries to a MySQL database made via
> SQLalchemy. I will need to make many complex queries, then do some
> simple statistical work on the results. But even the first query is
> taking a very long time. Any guidance you can gi
Hi,
on Suse 11.1 with gcc 4.3.2 installation stops early in pari-2.3.3.p0
with
/bin/sh: symbol lookup error: /home/henrik/Pakete/sage-3.2.1/local/
lib/libreadline.so.5: undefined symbol: PC
I am running on an x64_64 dual core notebook with Suse 11.1rc1.
Any help appreciated, thank you very mu
On Dec 19, 8:53 am, mhampton wrote:
Hi Marshall,
> I reran the test and it passed. sage -maxima works fine. I did
> realize that I said something incorrect, it looks like the install I
> am using was originally from the 3.2.1.rc0 source, and I have upgraded
> and renamed it several times si
I reran the test and it passed. sage -maxima works fine. I did
realize that I said something incorrect, it looks like the install I
am using was originally from the 3.2.1.rc0 source, and I have upgraded
and renamed it several times since then. So it is not too weird an
event. Some of the c sou
On Dec 19, 5:21 am, mhampton wrote:
> I had an interesting failure on an intel mac running 10.5. Let me
> describe my setup a bit since I think its relevant: because of the new
> upgrade flexibility, I decided to have a "stable" sage and an
> "unstable" sage on my machine, and I delete almost
Thanks for directing me.
The bottleneck appears to be queries to a MySQL database made via
SQLalchemy. I will need to make many complex queries, then do some
simple statistical work on the results. But even the first query is
taking a very long time. Any guidance you can give is greatly
appreciat
Can you give a little more detail about what you are doing? Do you
have an idea as to what the main bottleneck is in your computation?
Cheers,
Marshall Hampton
On Dec 18, 2:52 pm, Dan wrote:
> I have been using Sage for a fairly intense computational biology
> project. I have been very please
I had an interesting failure on an intel mac running 10.5. Let me
describe my setup a bit since I think its relevant: because of the new
upgrade flexibility, I decided to have a "stable" sage and an
"unstable" sage on my machine, and I delete almost all of my other
sage builds. I changed the sag
On Thursday 18 December 2008, Dan wrote:
> I have been using Sage for a fairly intense computational biology
> project. I have been very pleased with the software, but when it was
> finely time to run my computations I learned that my hardware was
> grossly inadequate. I have since gained access
On Dec 18, 2008, at 11:53 PM, mabshoff wrote:
> On Dec 18, 11:50 pm, Robert Bradshaw
> wrote:
>> On Dec 18, 2008, at 11:23 PM, mabshoff wrote:
>
> Hi,
>
>>> You can also upgrade by running
>>
>>> ./sage -upgradehttp://sage.math.washington.edu/home/mabshoff/
>>> release-cycles-3.2.2/sage-3.2.2/
25 matches
Mail list logo
