On 4/26/07, Jonathan William Bober <[EMAIL PROTECTED]> wrote:
>> There also seem to be some other issues which come from maxima. One
> example is
>
> sage: print B
> sqrt(3) I 1
> -- - -
>
There also seem to be some other issues which come from maxima. One
example is
sage: print B
sqrt(3) I 1
-- - -
22
sage: bool(B^3 == 1)
False
sage: bool(expand(B^3) == 1)
True
A
Thanks!!
On 4/26/07, Jonathan William Bober <[EMAIL PROTECTED]> wrote:
>
> Never mind all that - it seems that the fix is easy. Just after
>
> symbols = {operator.lt:' < ', operator.le:' <= ', operator.eq:' == ',
>operator.ne:' != ',
> operator.ge:' >= ', operator.gt:' > '
Never mind all that - it seems that the fix is easy. Just after
symbols = {operator.lt:' < ', operator.le:' <= ', operator.eq:' == ',
operator.ne:' != ',
operator.ge:' >= ', operator.gt:' > '}
maxima_symbols = dict(symbols)
maxima_symbols[operator.eq] = '='
in calculus/eq
On Apr 25, 4:43 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Is it even possible to create a pseudo-tty interface to a cygwin program
> from the MSVC compiled version of Python? The pexpect website
> says: "Pexpect does not currently work on the standard Windows Python
> (see the pty requir
On 4/25/07, mabshoff <[EMAIL PROTECTED]> wrote:
> > For a while we didn't support cygwin and only distributed SAGE using
> > colinux and/or vmware. But colinux isn't really that good for various
> > reasons (though performance wasn't bad), and vmware can be painful
> > as well -- the download for
On Apr 25, 6:27 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 4/24/07, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hello,
>
> > I did some googling and
>
> > a) The problem with "threadlist_ix -1" also happens with sage 2.4.2
> > with the current cygwin
> > b) The cygwin mailing list has
On 4/24/07, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I did some googling and
>
> a) The problem with "threadlist_ix -1" also happens with sage 2.4.2
> with the current cygwin
> b) The cygwin mailing list has lots of reports about "threadlist_ix
> -1" with lots of different executables (e
Hello,
I did some googling and
a) The problem with "threadlist_ix -1" also happens with sage 2.4.2
with the current cygwin
b) The cygwin mailing list has lots of reports about "threadlist_ix
-1" with lots of different executables (emacs, pari, tar ...), but so
far no solution to the problem. It
Hello,
it took a while, but I finally ran the doctests on cygwin and there
are definitely some problems:
The following tests failed:
sage -t calculus/calculus.py
sage -t calculus/functional.py
sage -t calculus/wester.py
sage -t lfunctions/sympow.py
s
It also builds fine for me under Ubuntu Edgy Eft, on an Intel Core Duo.
Like others have reported, the only doctest failures seem to be in
multi_polynomial_libsingular.pyx.
On Mon, 2007-04-23 at 02:35 -0700, William Stein wrote:
> Hi,
>
> I've posted a preliminary SAGE-2.5.alpha0 tarball here:
On Apr 23, 8:56 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > Also, at the end of the make process, I tried to type:
>
> > install_scripts ( '/scratch' )
>
> > using the syntax it recommended. It replied:
>
> You have to type it in SAGE not on the bash command line. I'll clarify
> this in
On 4/23/07, Bill Hart <[EMAIL PROTECTED]> wrote:
> I re-ran the tests and the same error recurred (but with a different
> numbered temp directory of course). I checked in the sage temp
> directory and there seemed to be two numbered temp directories in
> there, one of which did not change, the oth
William Stein wrote:
> On 4/23/07, Bill Hart <[EMAIL PROTECTED]> wrote:
>> Seems to build fine in 40 minutes on a dual core Pentium-D 32 bit 3.2
>> GHz with Fedora Core (no idea what version - if someone tells me how
>> to check, I will).
>
> No clue. Thanks.
>
uname -a
returns the name of th
I re-ran the tests and the same error recurred (but with a different
numbered temp directory of course). I checked in the sage temp
directory and there seemed to be two numbered temp directories in
there, one of which did not change, the other of which seemed to
change with the doctest being run.
William Stein wrote:
> Hi,
>
> I've posted a preliminary SAGE-2.5.alpha0 tarball here:
>
> /home/was/sage2.5
>
Linux paix.jaapspies.nl 2.6.20-1.2307.fc5smp #1 SMP Sun Mar 18 21:02:16 EDT
2007 i686 i686 i386 GNU/Linux
real74m15.263s
user60m38.879s
sys 9m37.326s
To install gap, g
On 4/23/07, Bill Hart <[EMAIL PROTECTED]> wrote:
> Seems to build fine in 40 minutes on a dual core Pentium-D 32 bit 3.2
> GHz with Fedora Core (no idea what version - if someone tells me how
> to check, I will).
No clue. Thanks.
> There were plenty of compiler warnings including ones about var
Seems to build fine in 40 minutes on a dual core Pentium-D 32 bit 3.2
GHz with Fedora Core (no idea what version - if someone tells me how
to check, I will).
There were plenty of compiler warnings including ones about variables
used uninitialised, incorrect C++ compiler directives used and the
li
Hi David,
Thanks for reporting those few minor failures. Those are, in fact,
extremely useful,
since I don't have an amd64 machine running suse, and it's extremely
important that all doctests pass on all known build machines. I've fixed the
corresponding doctests.
Now that you have sage-2.5, y
On Monday 23 April 2007 11:35, William Stein wrote:
> Hi,
>
> I've posted a preliminary SAGE-2.5.alpha0 tarball here:
>
> /home/was/sage2.5
>
> I'm uploading it now -- it's 93 MB, and I'm uploading it as I write this
> email. I don't know for certain that it builds, though hopefully it will
> bo
20 matches
Mail list logo
