Hello folks,
Sage 2.10.1.rc0 was nothing to write home about, but 2.10.1.rc1
should be much better and build out of the box on Linux, OSX 10.4
and 10.5. Since rc0 we merged 15 patches, some of them quite
invasive. So if you review a patch and/or bundle please make
sure it applies cleanly against
William Stein wrote:
[...]
>
> Could you try changing that line 150 of sage/interfaces/sage0.py to
> return eval(self.eval('cputime(%s)'%t).strip())
> then do "sage -br" and retry the test and see if it works on your machine?
> Let me know.
>
Removing
/home/jaap/downloads/sage-2.10.1
mabshoff wrote:
>
>
> On Jan 27, 3:00 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>> On Jan 26, 2008 11:46 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
[...]
>>
>> Thanks for reporting this!!
>
Hi Michael
> Yep, I remember now that somebody else reported this a week or so ago
> in sage-suppor
On Jan 27, 2008 4:55 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> William Stein wrote:
> [...]
> >
> > Could you try changing that line 150 of sage/interfaces/sage0.py to
> > return eval(self.eval('cputime(%s)'%t).strip())
> > then do "sage -br" and retry the test and see if it works on
William Stein wrote:
> On Jan 27, 2008 4:55 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>> William Stein wrote:
>> [...]
>>> Could you try changing that line 150 of sage/interfaces/sage0.py to
>>> return eval(self.eval('cputime(%s)'%t).strip())
>>> then do "sage -br" and retry the test and
On Jan 27, 2008 6:01 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> William Stein wrote:
> > On Jan 27, 2008 4:55 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
> >> William Stein wrote:
> >> [...]
> >>> Could you try changing that line 150 of sage/interfaces/sage0.py to
> >>> return eval(self
William Stein wrote:
>> ValueError: invalid literal for float(): ^[[0;31m
>> ^[[0m2.38963502
>> **
>> 1 items had failures:
>> 2 of 3 in __main__.example_2
>> ***Test Failed*** 2 failures.
>> For whitespace er
Jaap Spies wrote:
> William Stein wrote:
In
aString = self.eval('cputime(%s)'%t)
IDENTITY_MAP = ''.join([chr(x) for x in range(256)])
BAD_MAP = ''.join([chr(x) for x in range(32) + [124]])
aNewString = aString.translate(IDENTITY_MAP, BAD_MAP)
ret
On Jan 26, 2008 1:10 PM, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
> I believe the point of is_simplified() is to see if the result has
> already been simplified. Trying to detect if simplify() will modify
> self is a (potentially) expensive operation, so if it knows it's been
> simplified then i
mabshoff wrote:
> Hello folks,
>
[...]
>
> The tarball [201MB] is available at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/sage-2.10.1.rc1.tar
>
On Fedora 8 32 bits all tests passed.
Jaap
--~--~-~--~~~---~--~~
To post to this grou
On Jan 27, 2008, at 08:28 , Jaap Spies wrote:
>
> Jaap Spies wrote:
>> William Stein wrote:
>
>
> In
> aString = self.eval('cputime(%s)'%t)
> IDENTITY_MAP = ''.join([chr(x) for x in range(256)])
> BAD_MAP = ''.join([chr(x) for x in range(32) + [124]])
> aN
Justin C. Walker wrote:
>
> On Jan 27, 2008, at 08:28 , Jaap Spies wrote:
>
>> Jaap Spies wrote:
>>> William Stein wrote:
>>
>> In
>> aString = self.eval('cputime(%s)'%t)
>> IDENTITY_MAP = ''.join([chr(x) for x in range(256)])
>> BAD_MAP = ''.join([chr(x) for x in r
FYI,
There is IMO an interesting discussion going on in:
http://groups.google.com/group/sci.math.symbolic/topics
regarding bugs and bugs hunting in CAS.
Follow the 5 stars.
Jaap
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegrou
Hi,
It seems the __abs__ method for vectors is missing the part that is
supposed to square the components before they are added.
[e.g. abs(vector([1..5])) should really be
sqrt(1+4+9+16+25)=sqrt(55) ]
The code of the current version is included below.
def __abs__(self):
"""
Hello,
I've added this as #1954 and posted a patch.
--Mike
On Jan 27, 2008 3:50 PM, Peter <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> It seems the __abs__ method for vectors is missing the part that is
> supposed to square the components before they are added.
>
> [e.g. abs(vector([1..5])) should re
On Jan 27, 2008 6:50 PM, Peter <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> It seems the __abs__ method for vectors is missing the part that is
> supposed to square the components before they are added.
>
> [e.g. abs(vector([1..5])) should really be
> sqrt(1+4+9+16+25)=sqrt(55) ]
>
> The code of the cur
On Jan 27, 2008, at 24:55 , mabshoff wrote:
> Sage 2.10.1.rc0 was nothing to write home about, but 2.10.1.rc1
> should be much better and build out of the box on Linux, OSX 10.4
> and 10.5. Since rc0 we merged 15 patches, some of them quite
> invasive. So if you review a patch and/or bundle plea
On Jan 27, 2008 8:03 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 27, 2008, at 24:55 , mabshoff wrote:
>
> > Sage 2.10.1.rc0 was nothing to write home about, but 2.10.1.rc1
> > should be much better and build out of the box on Linux, OSX 10.4
> > and 10.5. Since rc0 we merged 15 pa
Does anyone know what's going on in the following example? I can't seem
to reproduce this with a simple example. Basically, I create a few
'callable symbolic expressions', and then define a lambda function that
calls a one of them.
Ultimately, I have a function
Q = lambda x : RR(bound(15000, 15
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
David Harvey made some interesting suggestions on sagetrac about #1014
(implementing a number-of-digits function). I have some comments about
this and I decided it might be better to bring the discussion to
sage-devel; I'll try to summarize what
On Jan 27, 2008, at 10:44 PM, Alex Ghitza wrote:
> David's suggestion was:
> - -
> * instead of computing the whole power, just estimate the top
> couple of
> digits using MPFR (much much much faster than computing the whole
> power)
> * keep increasing precision until we ca
On Jan 27, 2008 9:39 PM, Jonathan Bober <[EMAIL PROTECTED]> wrote:
>
> Does anyone know what's going on in the following example? I can't seem
> to reproduce this with a simple example. Basically, I create a few
> 'callable symbolic expressions', and then define a lambda function that
> calls a on
The escape sequences look like old ansi-graphics sequences.
Is there a terminal setting somewhere?
Tim
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more o
On Jan 27, 2008, at 10:55 PM, David Harvey wrote:
>> We actually know what the first few digits (or, actually, all of
>> them)
>> of *compare* are: 1000...
>
> Sorry, you're right, I wasn't very coherent.
>
> What I think I meant was to quickly compute the top few *binary*
> digits of "com
> So what do you, Jaap, and Craig Citro all have in common?
Rugged good looks? :)
Fix is up on trac ticket 1958. The issue is that ANSI codes end up in
the output string; I wrote a very quick and dirty patch to strip them
out, but it's still curious to me how they get there on our three
machines
On Jan 28, 5:53 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> On Jan 27, 2008, at 20:36 , Craig Citro wrote:
>
>
>
> >> So what do you, Jaap, and Craig Citro all have in common?
>
> > Rugged good looks? :)
>
> I certainly concur with this conclusion, but...
:)
> > Fix is up on trac ticke
> > Fix is up on trac ticket 1958. The issue is that ANSI codes end up in
> > the output string; I wrote a very quick and dirty patch to strip them
> > out, but it's still curious to me how they get there on our three
> > machines and nowhere else. Maybe a configuration issue? An issue with
> > re
On Jan 27, 2008, at 18:39 , Jonathan Bober wrote:
>
> Does anyone know what's going on in the following example? I can't
> seem
> to reproduce this with a simple example. Basically, I create a few
> 'callable symbolic expressions', and then define a lambda function
> that
> calls a one of th
On Jan 27, 2008, at 20:36 , Craig Citro wrote:
>
>> So what do you, Jaap, and Craig Citro all have in common?
>
> Rugged good looks? :)
I certainly concur with this conclusion, but...
> Fix is up on trac ticket 1958. The issue is that ANSI codes end up in
> the output string; I wrote a very qu
> > I'll suggest that this is more of a work-around than a fix. The
> > question remains, as you say, regarding the presence of these pesky
> > escape sequences...
> >
>
> Very true.
>
So I just posted another version of the patch, which is a bit slicker,
at William's suggestion. I need someone
30 matches
Mail list logo
