On Wed, 18 Jan 2012 at 10:59AM +0900, Dan Drake wrote:
> I've noticed that, too. But I just found that, in the README file of the
> Python source, I see:
>
> To test the interpreter, type "make test" in the top-level directory.
> This runs the test set twice (once with no compiled files, o
On Sun, 01 Jan 2012 at 08:02AM -0800, daveloeffler wrote:
> Here's another strange thing: with the new Python 2.7.2 spkg, if
> SAGE_CHECK is set, the whole Python test suite gets run *twice over*!
> Is this deliberate?
I've noticed that, too. But I just found that, in the README file of the
Python
Both the latest 4.8.alpha and this 5.0.prealpha build
and pass 'make ptestlong' on an up to date Ubuntu
11.10 amd64 system, provided, of course, that I first
'sudo apt-get remove libreadline-dev && sudo apt-get autoremove'
to enable 'r' to build without giving the longstanding
libreadline error.
Hi Jeroen!
On 31 Dez. 2011, 15:53, Jeroen Demeyer wrote:
> I have made an unofficial sage-5.0.prealpha0 release.
It builds on openSUSE 12.1, and "make ptestlong" works!
Is there a list of platforms that are "officially supported" and a
list of platforms that are not officially supported but on
On Mon, 02 Jan 2012 20:08:52 cch wrote:
> Make Sage with matplotlib by
> export SAGE_MATPLOTLIB_GUI='yes'
>
> and it stops with the error:
> ...
> Tkinter (IndexError: list index out of range)
> ...
>
> where tcltk-8.5.11 used in 64bit Slackware Linux.
>
> To solve this problem, I remove TCLTK a
Make Sage with matplotlib by
export SAGE_MATPLOTLIB_GUI='yes'
and it stops with the error:
...
Tkinter (IndexError: list index out of range)
...
where tcltk-8.5.11 used in 64bit Slackware Linux.
To solve this problem, I remove TCLTK auto-dect function in "src/
setupext.py" about at line 842.
And
On 2012-01-02 05:24, John H Palmieri wrote:
> Traceback (most recent call last):
> File "/storage/masiao/sage-5.0.prealpha0/local/bin/sage-run", line
> 6, in
> os.chdir(sys.argv[1])
> OSError: [Errno 2] No such file or directory: ''
> Error running Sage on example.sag
On 2012-01-02 05:24, John H Palmieri wrote:
> I think somewhere the current working directory is being changed, so
> when it's looking for 'example.sagetex.sage', it can't find it. I'm not
> sure though. My guess is that it's related to #11073.
The following code block from $SAGE_ROOT/sage shoul
On 2012-01-02 05:24, John H Palmieri wrote:
> I think somewhere the current working directory is being changed, so
> when it's looking for 'example.sagetex.sage', it can't find it. I'm not
> sure though. My guess is that it's related to #11073.
Yes, it is.
--
To post to this group, send an ema
Le 02/01/2012 10:50, daveloeffler a écrit :
(What does -lm mean?)
That's for the C math lib.
Snark on #sagemath
--
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, v
On Jan 1, 10:42 pm, John H Palmieri wrote:
> On Sunday, January 1, 2012 7:18:20 AM UTC-8, daveloeffler wrote:
>
> > I get an error when doing a parallel build with SAGE_CHECK set. See
> > below for the relevant part of the output. The problem seems to be
> > that the M4RIE test suite requires NT
On Jan 1, 10:42 pm, John H Palmieri wrote:
> On Sunday, January 1, 2012 7:18:20 AM UTC-8, daveloeffler wrote:
>
> > I get an error when doing a parallel build with SAGE_CHECK set. See
> > below for the relevant part of the output. The problem seems to be
> > that the M4RIE test suite requires NT
On Sunday, January 1, 2012 8:52:24 AM UTC-8, daveloeffler wrote:
>
>
> Here's *yet another* SAGE_CHECK issue. The sagetex package doesn't
> work:
>
[snip]
> Output written on example.dvi (7 pages, 23380 bytes).
> Transcript written on example.log.
> Traceback (most recent call last):
>
On Sunday, January 1, 2012 7:18:20 AM UTC-8, daveloeffler wrote:
>
> I get an error when doing a parallel build with SAGE_CHECK set. See
> below for the relevant part of the output. The problem seems to be
> that the M4RIE test suite requires NTL and Givaro to have already been
> built, but th
On 1 January 2012 16:52, daveloeffler wrote:
>
>
> Here's *yet another* SAGE_CHECK issue. The sagetex package doesn't
> work:
>
> sagetex-2.3.1.p1
> Machine:
> Linux selmer 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC
> 2009 x86_64 GNU/Linux
David, We should check whether this machine
On Jan 1, 4:38 pm, Volker Braun wrote:
> I'm only surprised that you get this far; I thought pretty much all builds
> with SAGE_CHECK='yes' die while testing Python because some optional
> modules don't get compiled.
Yes, well, test_distutils fails for me and always has done. I'm just
puzzled t
I'm only surprised that you get this far; I thought pretty much all builds
with SAGE_CHECK='yes' die while testing Python because some optional
modules don't get compiled.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sa
Here's another strange thing: with the new Python 2.7.2 spkg, if
SAGE_CHECK is set, the whole Python test suite gets run *twice over*!
Is this deliberate?
Here is the tail end of the first test run and the beginning of the
second:
test_zipimport_support
test_zlib
343 tests OK.
1 test failed:
I get an error when doing a parallel build with SAGE_CHECK set. See
below for the relevant part of the output. The problem seems to be
that the M4RIE test suite requires NTL and Givaro to have already been
built, but that Sage's build scripts don't know about these
dependencies. Installing the Giva
On 12/31/11 8:53 AM, Jeroen Demeyer wrote:
I have made an unofficial sage-5.0.prealpha0 release.
Just as a reminder, the AMS/MAA Joint Math Meetings start next
Wednesday, where we have a booth. I expect that a fair number of people
will be downloading Sage next week. It would be cool if 4.8
On 12/31/11 8:53 AM, Jeroen Demeyer wrote:
The flask notebook is not included yet, as it is not
quite ready to be merged yet.
You can test the flask notebook by following the instructions at
http://trac.sagemath.org/sage_trac/ticket/11080
You'd need to apply the dependencies at
http://trac.
21 matches
Mail list logo
