[sage-devel] Re: Binaries for Solaris and Cygwin

On Sunday, May 12, 2013 3:27:16 PM UTC+2, Jean-Pierre Flori wrote: > > Dear all, > > I've put binaries of Sage 5.9 for Solaris (10)/sparc and Cygwin at: > * http://boxen.math.washington.edu/home/jpflori/dist/ > As the one who herds the binaries on the mirrors, should I distribute them through t

Re: [sage-devel] Re: Binaries for Solaris and Cygwin

On 05/13/2013 11:17 AM, Harald Schilly wrote: On Sunday, May 12, 2013 3:27:16 PM UTC+2, Jean-Pierre Flori wrote: Dear all, I've put binaries of Sage 5.9 for Solaris (10)/sparc and Cygwin at: * http://boxen.math.washington.edu/home/jpflori/dist/

[sage-devel] [debian] Trouble building documentation

Hi, my experiments building sage with some spkg replaced with debian packages are progressing. It does compile, but when trying to build the documentation, things look like normal, but at the end of the first pass, it just stops, sitting there idle. I have to kill it and of course I then lack

Re: [sage-devel] Binaries for Solaris and Cygwin

On 12 May 2013 14:27, Jean-Pierre Flori wrote: > Dear all, > > I've put binaries of Sage 5.9 for Solaris (10)/sparc and Cygwin at: > * http://boxen.math.washington.edu/home/jpflori/dist/ > > They were generated as follows: > * export SAGE_FAT_BINARIES=yes > * make > * ./sage -bdist 5.9 > Not sure

[sage-devel] plugin,startup_modules failure

I'm trying to fix a plug-in failure for #14217 and I can't seem to find any information on what the error is. Below is the diff from the plug-in. The only thing that I can see is that it is not listing projective.projective_rational_point as a new module generic.rational_points as removed and

[sage-devel] Upgrade to PARI-2.5.4 (#14539) needs review

A straight-forward upgrade to PARI-2.5.4 needs review: http://trac.sagemath.org/sage_trac/ticket/14539 Thanks, Jeroen. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email

[sage-devel] bug or feature in power series representation?

While playing with ticket #10480 I have found a grey area in the representation of power series {{{ sage: K. = Qp(3)[[]] sage: f = 3^2*w + O(w^3) sage: g = O(3)*w sage: fg = f*g sage: fg 0 sage: fg == 0

[sage-devel] Re: plugin,startup_modules failure

Sage startup is slow (especially on high-latency file systems like NFS) because thousands of individual files have to be read when the import tree is evaluated starting at sage.all. Splitting up large files into multiple small ones like in your patch is great for code maintainability but hurts

[sage-devel] Re: plugin,startup_modules failure

So is the failure pointing out an increase in start-up time? Isn't that what the startup_time plug-in is checking for? (which actually showed a decrease in start-up time for this patch) I've added lazy_imports to my todo list as a faster sage start-up would be nice. On Monday, May 13, 2013 11:

[sage-devel] Re: plugin,startup_modules failure

Well that particular doctest run was on my desktop patchbot with everything cached into memory, so you won't see it on the startup time in this case. However if you run stuff over NFS then thats a whole different matter. On Monday, May 13, 2013 6:03:01 PM UTC+1, Ben Hutz wrote: > > So is the f

Re: [sage-devel] Re: plugin,startup_modules failure

FYI, it generates the list by inspecting sys.modules on a clean (re)start of sage before and after the patches are applied. There's no guerentee that it affects startup time (which is really noisy and hard to measure), but the fact that we import thousands of modules on startup, most of which are u

Re: [sage-devel] Binaries for Solaris and Cygwin

On 05/12/2013 03:27 PM, Jean-Pierre Flori wrote: Feel free to test or even use them, I can not guarantee anything is actualy working right (but at least sage computes 1+1 and returns 2). Note that for Cygwin you will still need to install Cygwin itself and the system-wide lapack packages; it migh

[sage-devel] SQRT of negative number is negative? Or positive? Or what?

Could anyone shed a bit of light on this? The more I try, the more SAGE's types get in my way. It turns out to be an unpredictable element. Unless I make sure *every* involved function really returns one specific type, calculations are becoming practically impossible, because the results are compl

Re: [sage-devel] Binaries for Solaris and Cygwin

On Monday, May 13, 2013 10:41:15 PM UTC+2, Jeroen Demeyer wrote: > > On 05/12/2013 03:27 PM, Jean-Pierre Flori wrote: > > Feel free to test or even use them, I can not guarantee anything is > > actualy working right (but at least sage computes 1+1 and returns 2). > > Note that for Cygwin you w

[sage-devel] Re: SQRT of negative number is negative? Or positive? Or what?

On Monday, May 13, 2013 2:11:59 PM UTC-7, ManDay wrote: > > Could anyone shed a bit of light on this? > > The more I try, the more SAGE's types get in my way. It turns out to be > an unpredictable element. Unless I make sure *every* involved function > really returns one specific type, calculati

Re: [sage-devel] Re: SQRT of negative number is negative? Or positive? Or what?

On 05/13/2013 04:56 PM, John H Palmieri wrote: > On Monday, May 13, 2013 2:11:59 PM UTC-7, ManDay wrote: > > Could anyone shed a bit of light on this? > > The more I try, the more SAGE's types get in my way. It turns out to be > an unpredictable element. Unless I make sure *every* inv

[sage-devel] Re: SQRT of negative number is negative? Or positive? Or what?

On Monday, May 13, 2013 2:11:59 PM UTC-7, ManDay wrote: > > Could anyone shed a bit of light on this? > > The more I try, the more SAGE's types get in my way. > It is pretty much understood by some people in the computer algebra system-building community that "types" or "categories" or similar

Re: [sage-devel] Re: SQRT of negative number is negative? Or positive? Or what?

Thank you John and the others, too. That clarifies it. I never used complex numbers in C (personally, I consider them, just like wchars, out of place but that's another subject...), if I had, I'd likely have known. It's not apparently clear how to solve this problem consistently (I'm just performi