On Thu, May 14, 2009 at 10:40:26PM -0700, mabshoff wrote:
> > > > * Solaris: I finally *fixed* the symmetrica issues and all it took
> > > > was 6 hours of staring at disgusting code.
> ...
> > And thanks so much for the investment you did into this.
> ...
> In the end I know that there are bits
On May 14, 2:00 pm, David Roe wrote:
> I've taken a look at most of these. I'll send Nicolas comments off list
> (though I probably won't get to that until later tonight). But I agree with
> Robert that a global picture wiki page would be good.
> David
Please keep review comments on list or
On May 14, 3:41 pm, Robert Bradshaw
wrote:
> On May 14, 2009, at 2:02 PM, Nicolas M. Thiery wrote:
> > I am trying to keep the patch description on trac up-to-date (from the
> > description in the patch itself):
>
> > http://sagetrac.org/sage_trac/ticket/5891
>
> > Suggestions for improve
On May 14, 1:18 pm, "Nicolas M. Thiery"
wrote:
> On Thu, May 14, 2009 at 08:34:56PM +0100, Martin Albrecht wrote:
Hi,
> > > * Solaris: I finally *fixed* the symmetrica issues and all it took
> > > was 6 hours of staring at disgusting code.
>
> > Congratulations!
Thanks.
> And thanks so muc
On May 14, 8:01 pm, Rado wrote:
Hi Rado,
> here is the patch as promised. I don't have a trac account and it
> seems closed, so someone needs to paste it there.
Follow http://wiki.sagemath.org/TracGuidelines and I will take care of
your account.
> http://www.math.uiuc.edu/~rkirov2/sage/1180
here is the patch as promised. I don't have a trac account and it
seems closed, so someone needs to paste it there.
http://www.math.uiuc.edu/~rkirov2/sage/11804.patch
Rado
On May 14, 7:12 am, Jason Grout wrote:
> Rado wrote:
> > alright, all tests passed. I will post the patch here tomorrow (i
-- Forwarded message --
From: Goran S. Ivanovic
Date: Thu, May 14, 2009 at 1:46 PM
Subject: Compiled Sage on Slackware 12.2
To: wst...@gmail.com
Hello Dr. Stein,
Just to let you know that I compiled SAGE on my Slack 12.2. I
installed it temporarily to see how the compilation pr
On May 14, 2009, at 2:02 PM, Nicolas M. Thiery wrote:
>
> Hi Robert!
>
> On Thu, May 14, 2009 at 01:25:35PM -0700, Robert Bradshaw wrote:
>> ...
>> I am looking forward to talking to you next week about all this
>> stuff, but I was thinking it would be useful to have a wiki page
>> summariz
On May 14, 2009, at 2:43 PM, Gonzalo Tornaria wrote:
> On Thu, May 14, 2009 at 4:45 PM, Robert Bradshaw
> wrote:
>>
>> On May 14, 2009, at 10:22 AM, Craig Citro wrote:
>>
I'm currently building/doctesting with (1) in place, and I'll
report
back soon. gen.pyx passes all tests, so
On Thu, May 14, 2009 at 4:45 PM, Robert Bradshaw
wrote:
>
> On May 14, 2009, at 10:22 AM, Craig Citro wrote:
>
>>> I'm currently building/doctesting with (1) in place, and I'll report
>>> back soon. gen.pyx passes all tests, so I suspect we're probably
>>> safe.
>>>
>>
>> Doctesting is done, and
Hi Robert!
On Thu, May 14, 2009 at 01:25:35PM -0700, Robert Bradshaw wrote:
> ...
> I am looking forward to talking to you next week about all this
> stuff, but I was thinking it would be useful to have a wiki page
> summarizing the "big picture" with the links to relevant tickets, or
I've taken a look at most of these. I'll send Nicolas comments off list
(though I probably won't get to that until later tonight). But I agree with
Robert that a global picture wiki page would be good.
David
On Thu, May 14, 2009 at 4:25 PM, Robert Bradshaw <
rober...@math.washington.edu> wrote:
On May 14, 2009, at 1:27 PM, Craig Citro wrote:
>
>> This is the right fix. Looks good--are you sure we don't use pari's
>> sum anywhere else?
>>
>
> Well, I'm not 100% sure ... but given that the Python and pari ones
> accept *different* numbers of arguments, I suspect we're okay. I tried
> usin
> This is the right fix. Looks good--are you sure we don't use pari's
> sum anywhere else?
>
Well, I'm not 100% sure ... but given that the Python and pari ones
accept *different* numbers of arguments, I suspect we're okay. I tried
using search_src to find cases with two or more commas in a call
On May 8, 2009, at 2:55 PM, Nicolas M. Thiery wrote:
>
> On Thu, May 07, 2009 at 12:55:57AM -0700, davidloeffler wrote:
>> Can I use this opportunity to request some reviews for modular forms
>> patches?
>
> Let me do the same for the prerequisite patches for the category
> framework. They are al
On Thu, May 14, 2009 at 08:34:56PM +0100, Martin Albrecht wrote:
>
> > * Solaris: I finally *fixed* the symmetrica issues and all it took
> > was 6 hours of staring at disgusting code.
>
> Congratulations!
And thanks so much for the investment you did into this.
I very much hope Alex will get
On May 14, 2009, at 10:22 AM, Craig Citro wrote:
>> I'm currently building/doctesting with (1) in place, and I'll report
>> back soon. gen.pyx passes all tests, so I suspect we're probably
>> safe.
>>
>
> Doctesting is done, and no troubles -- so I've posted a patch here:
>
> http://trac.sagema
> * Solaris: I finally *fixed* the symmetrica issues and all it took
> was 6 hours of staring at disgusting code.
Congratulations!
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http:/
2009/5/14 William Stein
>
> Just out of curiosity, do you think there is any chance that Maplesoft
> would provide any funding or help of any kind to an open source
> project whose mission statement is to to "Provide a viable free open
> source alternative to Maple"?
Obviously, I am speculating
On Thu, May 14, 2009 at 10:23 AM, Stephen Forrest
wrote:
> On 2009/5/7 Burcin Erocal wrote:
>
>> The director of R&D at Maple is Juergen Gerhard.
>
> A small correction: unless my information is out of date, as far as am I
> aware the person in charge of R+D at Maplesoft is still Laurent Bernard
On Thu, May 14, 2009 at 1:23 PM, Stephen Forrest
wrote:
> On 2009/5/7 Burcin Erocal wrote:
>
>> The director of R&D at Maple is Juergen Gerhard.
>
> A small correction: unless my information is out of date, as far as am I
> aware the person in charge of R+D at Maplesoft is still Laurent Bernardi
On 05/10/09 23:18, mabshoff wrote:
>>> Well, it doesn't matter for builds from source too much, the real
>>> problem is when a user runs -upgrade for Sage.
>> Sorry for being dense. You mean when the user runs -upgrade with a
>> non-framework install? Suppose a user has a fresh install, would the
On May 14, 10:50 am, Tim Abbott wrote:
Hi Tim,
> Sorry for the slow reply. sage-devel's Reply-To munging drops
> everyone from the Cc: on replies and I'm normally not directly
> subscribed to the list.
I tend to use Google groups directly and not bother with the email
interface.
> (because
On 05/13/09 22:16, Brian Granger wrote:
> I just pinged the pythonmac-sig group about why and when a framework
> build is actually needed. A while back I created an spkg for qt/pyqt
> and I remember that I needed to do a framework build to get it to
> work. My recollection is that if you want Py
On Thu, May 14, 2009 at 10:50 AM, Tim Abbott wrote:
>
> Sorry for the slow reply. sage-devel's Reply-To munging drops
> everyone from the Cc: on replies and I'm normally not directly
> subscribed to the list.
>
> (because of this kind of problem, I do think that everyone should run
> their high-
Sorry for the slow reply. sage-devel's Reply-To munging drops
everyone from the Cc: on replies and I'm normally not directly
subscribed to the list.
(because of this kind of problem, I do think that everyone should run
their high-traffic mailing lists without any sort of reply-to munging,
like t
Hello folks,
most 3.4.2 binaries are up on sagemath.org and being mirrored out.
>From the usual suspects some are still missing, i.e.
* Fedora Core 10 32 bit
* Atom
* RHEL 5.2/SLES 10 Itanium
* OSX 10.4 Intel
Most of the missing binaries will show up in the next 24 hours. We
also have some
I like Craig's solution (but have not yet tested his patch). Thanks, Craig!
John
2009/5/14 Craig Citro :
>
>> I'm currently building/doctesting with (1) in place, and I'll report
>> back soon. gen.pyx passes all tests, so I suspect we're probably safe.
>>
>
> Doctesting is done, and no troubles
Hi,
Anybody seen this or participated: https://fedoraproject.org/wiki/Classroom
This looks like a good idea to organize a Sage Classroom equivalent.
Jaap
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from
On 2009/5/7 Burcin Erocal wrote:
> The director of R&D at Maple is Juergen Gerhard.
A small correction: unless my information is out of date, as far as am I
aware the person in charge of R+D at Maplesoft is still Laurent Bernardin,
the vice-president of R+D. However, Juergen Gerhard deals with
> I'm currently building/doctesting with (1) in place, and I'll report
> back soon. gen.pyx passes all tests, so I suspect we're probably safe.
>
Doctesting is done, and no troubles -- so I've posted a patch here:
http://trac.sagemath.org/sage_trac/ticket/6039
-cc
--~--~-~--~~-
On Thu, May 14, 2009 at 12:34 PM, Jason Grout wrote:
>> Bill Page wrote:
>> Ok thanks. I recall the discussion and I can indeed write:
>>
>> sage: f=lambda x:RR(x).nth_root(3)
>> sage: f(-2.0)
>> -1.25992104989487
>>
>> but I think I'll let my earlier comment stand:
>>
I think there should be
On May 14, 9:46 am, Craig Citro wrote:
> > I don't think they would rename "sum" to please us!
>
> And I really really don't think they should. After all, the issue is
> that python and pari both use the same name for something -- we might
> as well be asking python to rename their sum funct
>>> Your comment about the sum function suggests to me that something
>>> similar might be behind the weird thing I reported yesterday.
>>
Yep, this is exactly the cause. If you look at rational.pyx, it
includes libs/pari/decl.pxi, which contains a declaration for Pari's
sum function. This then t
a bit of back and forth on the numpy list last night...
-- Forwarded message --
From: Glenn Tarbox, PhD
Date: Thu, May 14, 2009 at 1:31 AM
Subject: Re: [Numpy-discussion] numpy slices limited to 32 bit values?
To: Discussion of Numerical Python
On Wed, May 13, 2009 at 11:22 P
Rado wrote:
> alright, all tests passed. I will post the patch here tomorrow (its
> only two lines). Thanks for the explanations, now I understand what's
> the symlink for :)
and thanks for catching this and tracking down the fix!
Jason
--~--~-~--~~~---~--~~
To
On Thu, May 14, 2009 at 4:57 AM, John Cremona wrote:
>
> 2009/5/14 Michael Abshoff :
>>
>> On Thu, May 14, 2009 at 4:45 AM, John Cremona wrote:
>>>
>>> Your comment about the sum function suggests to me that something
>>> similar might be behind the weird thing I reported yesterday.
>>
>> Yeah,
On Thu, May 14, 2009 at 4:55 AM, David Joyner wrote:
>
>
> Will 4.0.a0 be released sometime today? (I'm leaving early tomorrow morning
> for SD15 and may not get internet access quickly when I arrive.)
Well, my main goal is to get ecl into 4.0.a0. Since the status meeting
from Thursday was bu
2009/5/14 Michael Abshoff :
>
> On Thu, May 14, 2009 at 4:45 AM, John Cremona wrote:
>>
>> Your comment about the sum function suggests to me that something
>> similar might be behind the weird thing I reported yesterday.
>
> Yeah, we ought to suggest to the pari people to rename such generic
I
On Thu, May 14, 2009 at 7:43 AM, mabshoff wrote:
>
>
...
>
> Ok, checking the wiki at http://wiki.sagemath.org/symbolics/pynac_todo/push
> three hours ago we were at
>
> == Doctest status: May 14 ==
>
> As of 1:03am, we have 66 failures in 18 files.
>
...
> sage -t devel/sage-symbolics/sage
On Thu, May 14, 2009 at 4:45 AM, John Cremona wrote:
>
> Your comment about the sum function suggests to me that something
> similar might be behind the weird thing I reported yesterday.
Yeah, we ought to suggest to the pari people to rename such generic
function. Even with C++ code in Sage havi
Your comment about the sum function suggests to me that something
similar might be behind the weird thing I reported yesterday.
If you take a fresh clone of 3.4.2, and in the file
sage/rings/rational.pyx add this function:
def dummy(self):
return sum([a for a in self.list()],0)
say a
On May 14, 4:31 am, mabshoff wrote:
> Ok, *still* no alpha (I caught up with sleep yesterday-ish), but here
> we go:
>
> * 75% coverage: Still at 74.4%, but pynac will get us over 75%.
>
> * pynac: Number of failing doctests keesp decreasing - I am not
> keeping track of this, so somebody els
Ok, *still* no alpha (I caught up with sleep yesterday-ish), but here
we go:
* 75% coverage: Still at 74.4%, but pynac will get us over 75%.
* pynac: Number of failing doctests keesp decreasing - I am not
keeping track of this, so somebody else has to update on this
* 64 bit OSX: does now pa
alright, all tests passed. I will post the patch here tomorrow (its
only two lines). Thanks for the explanations, now I understand what's
the symlink for :)
Rado
On May 14, 3:39 am, mabshoff wrote:
> On May 14, 1:32 am, Robert Bradshaw
> wrote:
>
> > On May 14, 2009, at 1:18 AM, Rado wrote:
>
On May 14, 1:32 am, Robert Bradshaw
wrote:
> On May 14, 2009, at 1:18 AM, Rado wrote:
>
> > Last question if I used ./sage -clone myvrr and made the changes in
> > myver, how do I tell sage to run the tests there (if this even makes
> > sense?)
>
> You can do
>
> ./sage -t devel/sage-myvrr/sage
On May 14, 2009, at 1:18 AM, Rado wrote:
> Last question if I used ./sage -clone myvrr and made the changes in
> myver, how do I tell sage to run the tests there (if this even makes
> sense?)
You can do
./sage -t devel/sage-myvrr/sage/graphs/... # or -tp 10
- Robert
>
> Rado
>
> On May 14, 3
Last question if I used ./sage -clone myvrr and made the changes in
myver, how do I tell sage to run the tests there (if this even makes
sense?)
Rado
On May 14, 3:13 am, mabshoff wrote:
> On May 14, 1:08 am, Rado wrote:
>
> > The bug is almost trivial. The code
>
> > verts = data.keys()
> > ..
On Wed, May 13, 2009 at 11:56:53PM -0700, Nick Alexander wrote:
> On 13-May-09, at 10:53 PM, Nicolas M. Thiery wrote:
> > On Tue, May 12, 2009 at 05:40:46PM -0700, Nick Alexander wrote:
> >>> - C-C C-j seems to get confused by tabs in the input, and triggers
> >>> automatic completion:
> >>
> >>
On May 14, 1:08 am, Rado wrote:
> The bug is almost trivial. The code
>
> verts = data.keys()
>
> for u in data:
> verts.union([v for v in data[u] if v not in verts])
>
> is slowing down because in python searching in lists is slow. If we
> use "verts = set(data.keys())" the code speeds
The bug is almost trivial. The code
verts = data.keys()
for u in data:
verts.union([v for v in data[u] if v not in verts])
is slowing down because in python searching in lists is slow. If we
use "verts = set(data.keys())" the code speeds up tremendously.
sage: D={}
sage: for i in xrange
On May 14, 12:42 am, Brian Granger wrote:
> > As is Sage doesn't even build if you do a straight up framework build.
> > This can and will be fixed, but if I have learned one thing about
> > FrameWorks on OSX is to avoid them whenever possible, i.e that
> > absolute crap issue with the IOKit an
> As is Sage doesn't even build if you do a straight up framework build.
> This can and will be fixed, but if I have learned one thing about
> FrameWorks on OSX is to avoid them whenever possible, i.e that
> absolute crap issue with the IOKit and libpng has scared me for
> life ;)
What are the cu
On Wed, May 13, 2009 at 9:13 AM, Brian Granger wrote:
>
>> Well, I think what we should do is merge as much of SPD into Sage as
>> possible to lessen the maintainance burden. One thing I could see here
>> is to define SAGE_EXECUTABLE and you would just set it to spd in your
>> code.
>
> I think t
54 matches
Mail list logo
