Re: [sage-devel] Few standard packages have sage-check to check them.

On 06/19/10 11:24 PM, William Stein wrote: On Saturday, June 19, 2010, Dr. David Kirkby wrote: I've just done a quick check to see the number of standard packages in Sage which have a file 'spkg-check' which will execute a test routine after building in the event the environment variable SAGE

[sage-devel] Re: mathematically correct eigen* methods of matrices.

I have sent a patch to ticket 8974 that implements this feature. http://trac.sagemath.org/sage_trac/ticket/8974 It is mixed with the implementation of this functions for endomorphisms. I hope thats not a problem. Miguel. -- To post to this group, send an email to sage-devel@googlegroups.com To

[sage-devel] Dead easy 4 line review needed.

If anyones got a minute or two, the following package needs review. It should not take long, or be difficult, as there are only 4 lines changed (excluding comments). http://trac.sagemath.org/sage_trac/ticket/9277 The changes do two things. 1) Allows the Flint test suite to build 64-bit by ad

[sage-devel] Re: jsmath image fonts not working with sage-4.4.3?

On Jun 19, 3:56 pm, William Stein wrote: > On Sat, Jun 19, 2010 at 12:32 PM, Kevin Horton wrote: > > On Jun 19, 3:12 pm, Kevin Horton wrote: > >>  just noted that the jsmath image fonts are not working for me with > >> sage-4.4.3. > > > I should have looked deeper in the sage-devel archives.  I

Re: [sage-devel] Few standard packages have sage-check to check them.

On 06/19/10 11:24 PM, William Stein wrote: On Saturday, June 19, 2010, Dr. David Kirkby wrote: I've just done a quick check to see the number of standard packages in Sage which have a file 'spkg-check' which will execute a test routine after building in the event the environment variable SAGE

Re: [sage-devel] Few standard packages have sage-check to check them.

On Saturday, June 19, 2010, Dr. David Kirkby wrote: > I've just done a quick check to see the number of standard packages in Sage > which have a file 'spkg-check' which will execute a test routine after > building in the event the environment variable SAGE_CHECK is set to yes. > > The number is

Re: [sage-devel] How was #8049 (libgfortran issue) solved?

On Sat, Jun 19, 2010 at 1:29 PM, Dr. David Kirkby wrote: > On 06/19/10 07:49 PM, William Stein wrote: >> >> On Fri, Jun 11, 2010 at 6:00 PM, Dr. David Kirkby >>  wrote: >>> >>> http://trac.sagemath.org/sage_trac/ticket/8049 >>> >>> was marked as a blocker by William, then marked as fixed. But the

[sage-devel] Re: local Python install screws up build of Sage.

IMHO it happens also on MacOSX when there is e.g. fink (a certain bunch of Unix utilities, based on Linux Debian distribution) installed. So it conflicts with e.g. the standard Apple's version of gcc, etc etc. Dima On Jun 19, 10:38 pm, "Dr. David Kirkby" wrote: > I've created this ticket in resp

[sage-devel] Few standard packages have sage-check to check them.

I've just done a quick check to see the number of standard packages in Sage which have a file 'spkg-check' which will execute a test routine after building in the event the environment variable SAGE_CHECK is set to yes. The number is depressingly small, at only 19. ./atlas-3.8.3.p12/spkg-check

Re: [sage-devel] local Python install screws up build of Sage.

On 06/19/10 09:38 PM, Dr. David Kirkby wrote: I've created this ticket in response to a problem noticed by someone else on Linux, and the same problem seen by me on Solaris. http://trac.sagemath.org/sage_trac/ticket/9209 Under some circumstances, having a local copy of python on a machine can s

[sage-devel] local Python install screws up build of Sage.

I've created this ticket in response to a problem noticed by someone else on Linux, and the same problem seen by me on Solaris. http://trac.sagemath.org/sage_trac/ticket/9209 Under some circumstances, having a local copy of python on a machine can screw up Sage. Any thoughts how this might be

Re: [sage-devel] How was #8049 (libgfortran issue) solved?

On 06/19/10 07:49 PM, William Stein wrote: On Fri, Jun 11, 2010 at 6:00 PM, Dr. David Kirkby wrote: http://trac.sagemath.org/sage_trac/ticket/8049 was marked as a blocker by William, then marked as fixed. But there is nothing there to indicate how it was fixed. Was the fix to manually copy th

[sage-devel] Upgrading Docutils, Pygments and Sphinx

Hi there, In the process of writing a patch for #9128 ("Sphinx should be aware of all.py to find its links"), I realized that the feature I was trying to achieve will be much easier with the new version of Sphinx. However, the new version 1.0 is still in beta2 so we probably want to wait for

Re: [sage-devel] Re: jsmath image fonts not working with sage-4.4.3?

On Sat, Jun 19, 2010 at 12:32 PM, Kevin Horton wrote: > On Jun 19, 3:12 pm, Kevin Horton wrote: >>  just noted that the jsmath image fonts are not working for me with >> sage-4.4.3. > > I should have looked deeper in the sage-devel archives.  It seems that > the issue mentioned in the following

[sage-devel] Re: jsmath image fonts not working with sage-4.4.3?

On Jun 19, 3:12 pm, Kevin Horton wrote: >  just noted that the jsmath image fonts are not working for me with > sage-4.4.3. I should have looked deeper in the sage-devel archives. It seems that the issue mentioned in the following thread, and Trac ticket 9276, is not yet fixed:

[sage-devel] jsmath image fonts not working with sage-4.4.3?

just noted that the jsmath image fonts are not working for me with sage-4.4.3. I have installed the optional jsmath image fonts package: % sage -optional Using SAGE Server http://www.sagemath.org//packages http://www.sagemath.org//packages/optional/list --> /home/kwh/sage-4.4.3/tmp/list *

Re: [sage-devel] questions about sage/databases/*

On Sat, Jun 12, 2010 at 5:04 AM, Alex Ghitza wrote: > > Dear sage-devels, > > The directory sage/databases has a dismal coverage score of 34.6%, and > a lot of the code is part of revision 0 in the hg repository (aka > sage-0.10.12 aka the Jurassic era).  This makes it rather fun to > document, an

Re: [sage-devel] How was #8049 (libgfortran issue) solved?

On Fri, Jun 11, 2010 at 6:00 PM, Dr. David Kirkby wrote: > http://trac.sagemath.org/sage_trac/ticket/8049 > > was marked as a blocker by William, then marked as fixed. But there is > nothing there to indicate how it was fixed. Was the fix to manually copy the > libgfortran library every time a bin

Re: [sage-devel] Re: Inclusion of external library and compatibility between licenses ...

On Tue, Jun 8, 2010 at 12:08 AM, Jason Grout wrote: > On 6/7/10 4:47 PM, William Stein wrote: >> >> On Mon, Jun 7, 2010 at 1:37 PM, Robert Bradshaw >>  wrote: >>> >>> On Jun 7, 2010, at 1:23 PM, Nathann Cohen wrote: >>> > Well, there's a technical and legal question here. On a technical note,

[sage-devel] Re: Sage-Notebook file format

Hi Ralf, You might glean a few more insights about the notebook file format from the project to convert latex documents to Sage worksheets. IIRC the current state of the Python conversion script there creates an sws file "from scratch", ie without using any Sage code. http://wiki.sagemath.org/de

Re: [sage-devel] Re: Relevant Sessions at upcoming Joint Meetings

On Tue, Jun 15, 2010 at 11:48 PM, William Stein wrote: > On Tue, Jun 15, 2010 at 8:43 PM, mhampton wrote: >> >> >>> >>> That doesn't mean we shouldn't do it, but the point is that funding >>> would be a relatively trivial issue compared to staffing.  Any >>> takers?  I guess Marshall and I are vo

Re: [sage-devel] bug in deps

Thanks. The below is now trac #9724: http://trac.sagemath.org/sage_trac/ticket/9274 On Thu, May 20, 2010 at 10:27 PM, carl hansen wrote: > Here is an excerpt from "deps" , the makefile in spkg/standard > > $(INST)/$(FORTRAN): >        $(SAGE_SPKG) $(FORTRAN) 2>&1 > > $(INST)/$(F2C): $(INST)/

Fwd: Fwd: [sage-devel] Re: Bug: Elliptic Curve Point Counting

Hi, Here is the official advice from the director of the PARI project about which version of Pari we should include in Sage-4.x and Sage-5.0: -- Forwarded message -- From: Karim Belabas Date: Thu, Apr 29, 2010 at 12:11 AM Subject: Re: Fwd: [sage-devel] Re: Bug: Elliptic Curve Po

[sage-devel] Re: SEP

Hello, Ralf! Ralf Hemmecke writes: >> For the reasons Robert Bradshaw mentioned, I don't think the AutoTools >> SEP makes a lot of sense for Sage. > > Robert also added > > "Automake would add another level of complexity to the build process, in > particular one which is not understood by many

Re: [sage-devel] Re: pushing towards 90% doctest coverage for Sage 5.0

On Tue, Jun 15, 2010 at 3:56 AM, daveloeffler wrote: > (I'm working on a couple of tickets but I can't remember my Sage wiki > account password -- can someone with admin rights reset it for me?) As far as I know, nobody knows how to reset Sage wiki passwords. Just make a new account with a slight

[sage-devel] doctest elliptic_curves/BSD.py reports "file not found"

BSD.py was a doctest which was failing on older hardware, or unsuitable hardware like 't2'. Robert Miller's fix at http://trac.sagemath.org/sage_trac/ticket/9127 worked for me, but now what is integrated into sage-4.4.4.alpha1 is not working. Instead it reports "file not found" On my Sun Bl

Re: [sage-devel] Sage-Notebook file format

Hi Ralf > I realized that the .sws File of a notebook is not a text file. > Would it be hard to also provide a text format that one could edit with > any editor? > > What I see, when I press the "Edit" button already doesn't look too bad. > Also when pressing the "Text" button, the notebook

Re: [sage-devel] Should MPC (for arithmetic of complex numbers) be a standard Sage package?

On 06/19/10 03:57 PM, William Stein wrote: On Sat, Jun 19, 2010 at 7:51 AM, Dr. David Kirkby * I personally believe the MPC library code should be of high quality as it is produced by a team of developers who in my personal opinion care about quality. (You know I've been a bit critical of so

Re: [sage-devel] Re: Sage-Notebook file format

On Fri, Jun 18, 2010 at 5:38 AM, Ralf Hemmecke wrote: > On 06/18/2010 01:55 PM, ma...@mendelu.cz wrote: >> Hi, sws it is gzipped (or bzipped) tar fille. Unzip, untar and > > bzipped and tarred... ;-) > > OK that helps. Thanks. > >> you should see text version and directories, one subdirectory for

[sage-devel] Negative sign missing in latex output

Example: {{{ var('q r') fp = q / r fn = -q / r + r / -q print(fp) print(fn) show(fp) show(fn) html("$fp = %s$"%(latex(fp))) html("$fn = %s$"%(latex(fn))) }}} Output: {{{ q/r -q/r - r/q \newcommand{\Bold}[1]{\mathbf{#1}}\frac{q}{r} \newcommand{\Bold}[1]{\mathbf{#1}}\frac{q}{r} + \frac{r}{q} fp

[sage-devel] Re: only-optional

On Jun 19, 12:23 am, David Kirkby wrote: > On 19 June 2010 03:55, John H Palmieri wrote: > > > > > > > On Jun 18, 5:38 pm, Robert Miller wrote: > >> On Fri, Jun 18, 2010 at 5:21 PM, John H Palmieri > >> wrote: > > >> > Is the proper syntax documented anywhere?  I can't find it. > > > Okay, see

Re: [sage-devel] Should MPC (for arithmetic of complex numbers) be a standard Sage package?

On Sat, Jun 19, 2010 at 7:51 AM, Dr. David Kirkby wrote: > The following ticket > > http://trac.sagemath.org/sage_trac/ticket/4446 > > is a long-standing ticket to add the MPC library for the arithmetic of > complex numbers with arbitrarily high precision as a *standard* item. (It > can't easily b

[sage-devel] Should MPC (for arithmetic of complex numbers) be a standard Sage package?

The following ticket http://trac.sagemath.org/sage_trac/ticket/4446 is a long-standing ticket to add the MPC library for the arithmetic of complex numbers with arbitrarily high precision as a *standard* item. (It can't easily be made optional - at least not in its current form). It has been

[sage-devel] Re: ECL/ maxima. We are in a bit of a mess.

Yeah, that could be useful for IRC too :) -Marshall On Jun 18, 12:19 pm, William Stein wrote: > On Friday, June 18, 2010, Dr. David Kirkby wrote: > > I need to do something else now (my wife will kill me if I stay on this > > computer much longer!) But I've left a few notes on the ticket. > >

[sage-devel] Re: [Ecls-list] OpenSolaris issue : Error: suffix or operands invalid for `mov'

On Sat, Jun 19, 2010 at 9:59 AM, David Kirkby wrote: > It does not look to me like Maxima is being compiled - at least not in > the sense of using a compiler like gcc. > Tthen it means that ECL itself is not capable of loading. If I interpret that the error is due to the causes shown in the link

[sage-devel] Re: [Ecls-list] OpenSolaris issue : Error: suffix or operands invalid for `mov'

On 19 June 2010 08:32, Juan Jose Garcia-Ripoll wrote: > On Sat, Jun 19, 2010 at 12:22 AM, Dr. David Kirkby > wrote: >> >> I should have added, the option >> --without-dffi >> was already added to ECL - without it, ECL would not build. > > Of course, because of the error message you showed before,

[sage-devel] Re: [Ecls-list] OpenSolaris issue : Error: suffix or operands invalid for `mov'

On Sat, Jun 19, 2010 at 12:22 AM, Dr. David Kirkby wrote: > I should have added, the option > --without-dffi > was already added to ECL - without it, ECL would not build. Of course, because of the error message you showed before, which was due to not using --without-dffi. > However, although t

Re: [sage-devel] Re: only-optional

On 19 June 2010 03:55, John H Palmieri wrote: > On Jun 18, 5:38 pm, Robert Miller wrote: >> On Fri, Jun 18, 2010 at 5:21 PM, John H Palmieri >> wrote: >> >> > Is the proper syntax documented anywhere?  I can't find it. > > Okay, see > >  http://trac.sagemath.org/sage_trac/ticket/9270 > > for do