[sage-devel] Should build errors automatically report system information?

2010-06-26 Thread Dr. David Kirkby
Currently if a package fails to build in Sage, one gets a message like: sage: An error occurred while installing pynac-0.2.0.p3 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /export/home/drkir

Re: [sage-devel] Should build errors automatically report system information?

2010-06-26 Thread William Stein
On Sat, Jun 26, 2010 at 12:04 AM, Dr. David Kirkby wrote: > Currently if a package fails to build in Sage, one gets a message like: > > > sage: An error occurred while installing pynac-0.2.0.p3 > Please email sage-devel http://groups.google.com/group/sage-devel > expla

Re: [sage-devel] Should build errors automatically report system information?

2010-06-26 Thread Robert Bradshaw
On Jun 26, 2010, at 12:04 AM, Dr. David Kirkby wrote: Currently if a package fails to build in Sage, one gets a message like: sage: An error occurred while installing pynac-0.2.0.p3 Please email sage-devel http://groups.google.com/group/sage-devel explaining the p

Re: [sage-devel] Should build errors automatically report system information?

2010-06-26 Thread Dr. David Kirkby
On 06/26/10 08:33 AM, William Stein wrote: On Sat, Jun 26, 2010 at 12:04 AM, Dr. David Kirkby wrote: Currently if a package fails to build in Sage, one gets a message like: sage: An error occurred while installing pynac-0.2.0.p3 Please email sage-devel http://grou

Re: [sage-devel] Should build errors automatically report system information?

2010-06-26 Thread Alex Ghitza
I think the point William is making is that if the main message to the user: > >> > >> sage: An error occurred while installing pynac-0.2.0.p3 > >> Please email sage-devel http://groups.google.com/group/sage-devel > >> explaining the problem and send the relevant par

[sage-devel] Re: Test your Python build

2010-06-26 Thread Adam Webb
> > I would not rule out any unexpected side-effects of some old patch > > though. It is probably a good idea to review the patches to remove > > anything that is no longer needed. > > > Adam > > Hi Adam. > > I noticed there was a patch to disutils in Sage, but removing it did not allow > it to b

Re: [sage-devel] Should build errors automatically report system information?

2010-06-26 Thread Dr. David Kirkby
On 06/26/10 09:44 AM, Alex Ghitza wrote: I think the point William is making is that if the main message to the user: sage: An error occurred while installing pynac-0.2.0.p3 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem an

[sage-devel] Where do I alter the flags for this bit of code ?

2010-06-26 Thread Dr. David Kirkby
I'm trying to build Sage on OpenSolaris and seem to be 99% there now. I'm hoping I can get it built before you guys can build Sage on Cygwin:) It may be impossible to build R in the short term, but long term that can probably be overcome. I could live with Sage not having R myself. This bit o

[sage-devel] Re: Clickable OS X app for 4.4.4

2010-06-26 Thread Jason Grout
On 6/24/10 8:53 AM, Ivan Andrus wrote: I don't know if there is work being done to create the clickable applications for OS X for this release (I know being release manager is hard enough), so I took the liberty of creating one, for intel at least. I created them on my MacBook Pro: Thanks!

[sage-devel] Re: Suggestion to make reporting bugs upstream MANDATORY for Positive review.

2010-06-26 Thread Jason Grout
On 6/24/10 5:54 AM, Dr. David Kirkby wrote: Here's a suggestion, which I think could be useful. If a reviewer sees that a bug on trac is an upstream bug, that they are required to see evidence that this has been reported upstream before the fix gets a positive review. Hence AUTHOR MUST state h

[sage-devel] Re: What are the most important parts of Sage?

2010-06-26 Thread Jason Grout
On 6/21/10 3:18 PM, Dr. David Kirkby wrote: On 06/21/10 10:09 PM, Robert Bradshaw wrote: On Jun 21, 2010, at 2:03 PM, Dr. David Kirkby wrote: It seem strange we are only checking about 20% of the packages, even if SAGE_CHECK is yes. Yes, I guess you could say we trust the upstream testing t

[sage-devel] upgrading pari to 2.4.3.SVN

2010-06-26 Thread William Stein
Hi, FYI, we're working on upgrading pari to 2.4.3 SVN at Sage Days. http://trac.sagemath.org/sage_trac/ticket/9343 -- William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubs

[sage-devel] Multivariate polynomial multiplication

2010-06-26 Thread Ryan Hinton
There was a flurry of activity a while ago (http://groups.google.com/ group/sage-devel/browse_thread/thread/ f5b976c979a3b784/6ca3d61f4347daf4) regarding multivariate polynomial multiplication. I am working on asymptotic expansions for a set of generating functions, and this feature will really he

Re: [sage-devel] Re: Test your Python build

2010-06-26 Thread Peter Jeremy
On 2010-Jun-25 18:55:24 +0100, "Dr. David Kirkby" wrote: >On 06/25/10 08:11 AM, Adam Webb wrote: >> I would not rule out any unexpected side-effects of some old patch >> though. It is probably a good idea to review the patches to remove >> anything that is no longer needed. > >I do wonder if ther

[sage-devel] Re: What are the most important parts of Sage?

2010-06-26 Thread kcrisman
> Matplotlib would be a good package to run tests on.  If maxima has a > test suite, that would seem pretty important to run too. > Maxima definitely has a test suite, perhaps even several (one involving contributed packages, one not)? It would be awesome to run those with SAGE_CHECK on. - kcri

Re: [sage-devel] Re: Clickable OS X app for 4.4.4

2010-06-26 Thread Ivan Andrus
On Jun 26, 2010, at 11:13 AM, Jason Grout wrote: > On 6/24/10 8:53 AM, Ivan Andrus wrote: >> I don't know if there is work being done to create the clickable >> applications for OS X for this release (I know being release manager is hard >> enough), so I took the liberty of creating one, for inte