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
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
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
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
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:
> 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 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
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
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
On Jan 27, 3:00 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Jan 26, 2008 11:46 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > mabshoff wrote:
> > > On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> > > dortmund.de> wrote:
> > >> 2.10.1.alpha2 turned out to be a disaster to put
On Jan 26, 2008 11:46 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> mabshoff wrote:
> > On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> > dortmund.de> wrote:
> >> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
> >> the rc0 que at
> >>
> >> http://sage.math.washington.edu/
mabshoff wrote:
>
>
> On Jan 26, 11:29 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
>> mabshoff wrote:
>>> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
>>> dortmund.de> wrote:
2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
the rc0 que at
http://sage.math.wa
On Jan 26, 11:29 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
> mabshoff wrote:
> > On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> > dortmund.de> wrote:
> >> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
> >> the rc0 que at
>
> >>http://sage.math.washington.edu/home/mabs
On Jan 26, 11:14 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> R Build fail on OS X (10.4, intel)
>
Hi Robert,
I will be checking into this, but it will be a while until I will
finish my OSX build.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group
mabshoff wrote:
> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> dortmund.de> wrote:
>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
>> the rc0 que at
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>>
>> rc0 should be out sooner rather
R Build fail on OS X (10.4, intel)
On Jan 26, 2008, at 11:46 AM, Jaap Spies wrote:
>
> mabshoff wrote:
>> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
>> dortmund.de> wrote:
>>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check
>>> out
>>> the rc0 que at
>>>
>>> http://sag
mabshoff wrote:
> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> dortmund.de> wrote:
>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
>> the rc0 que at
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>>
>> rc0 should be out sooner rather t
mabshoff wrote:
> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> dortmund.de> wrote:
>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
>> the rc0 que at
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>>
>> rc0 should be out sooner rather t
On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
> the rc0 que at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>
> rc0 should be out sooner rather than later. If you want to
2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
the rc0 que at
http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
rc0 should be out sooner rather than later. If you want to build
yourself you need the new r.spkg (p12 to be exact) and Sage-2.10.1.rc0-
e
As a general info: I broke R and rpy:
a) R is broken for parallel make. I did fix that.
b) rpy still thinks it is linking against RLapack on non-OSX, which we
no longer build there. Since the old Sage directory I also build the
new r.spkg against contained a copy of libR* in local/lib this didn'
On Jan 26, 5:06 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Jan 25, 2008 6:15 PM, mabshoff
>
> <[EMAIL PROTECTED]> wrote:
>
> > Hello folks,
>
> > Not much happened since alpha1, but 25 tickets closed are enough
> > reason to do an alpha2 release. The notebook issue hasn't been
> > fixed
On Jan 25, 2008 6:15 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> Not much happened since alpha1, but 25 tickets closed are enough
> reason to do an alpha2 release. The notebook issue hasn't been
> fixed yet and the ATLAS build improvements for Pentium M and
> Athlon still aren't m
23 matches
Mail list logo
