### [sage-devel] Re: sage-2.8.7

On Oct 16, 4:26 pm, David Joyner [EMAIL PROTECTED] wrote: Hi David, This version does not upgrade or install on suse 9.1 amd64. As far as I can tell Suse 9.1 AMD64 ships with gcc 3.3, which is not C99 conform. So flint won't build, you need at least gcc 3.4 or higher. I would not make it

### [sage-devel] Re: sage-2.8.7

On Oct 16, 5:46 pm, David Joyner [EMAIL PROTECTED] wrote: On 10/16/07, mabshoff [EMAIL PROTECTED] wrote: On Oct 16, 4:26 pm, David Joyner [EMAIL PROTECTED] wrote: Hi David, Hi David, This version does not upgrade or install on suse 9.1 amd64. As far as I can tell Suse 9.1

### [sage-devel] Re: sage-2.8.7

On Oct 16, 6:09 pm, David Joyner [EMAIL PROTECTED] wrote: On 10/16/07, mabshoff [EMAIL PROTECTED] wrote: Hi David, SNIP gcc blows up, there is little we can do about that. Please check if there are updates compilers available for SuSE 10.2. If not you can either install your own gcc

### [sage-devel] Re: Another cython?

On Oct 16, 7:23 pm, John Voight [EMAIL PROTECTED] wrote: This must be a different cython, no? http://campbell.nu/oscar/cython/cython-doc.html Weird! Definitely, but it is something completely different. It also seems dead, last update was at the end of 2000. JV Cheers, Michael

### [sage-devel] Re: Secure Notebook Deployment

On Oct 17, 1:09 am, William Stein [EMAIL PROTECTED] wrote: On 10/16/07, Timothy Clemans [EMAIL PROTECTED] wrote: I don't think it is the main jails you would block since they have to receive and send data in order for the public to access them. Maybe you would block the pool of sage__

### [sage-devel] Re: NTL build issues

On Oct 17, 7:45 pm, William Stein [EMAIL PROTECTED] wrote: On 10/17/07, Mike Hansen [EMAIL PROTECTED] wrote: I just upgraded to Ubuntu 7.10, and I have some issues building the NTL wrapper. Try moving your sage-main repository and trying again with a clean one, then pull in the

### [sage-devel] Bug Day 4 reminder: October 20th, 2007, 10am PST till ...

Hello, this Saturday, October 20th 2007, starting at 10am pacific standard time will be Bug Day 4. It will go on officially for about 10 hours, but it is pretty much open ended ;). Everybody is welcome to join in #sage-devel and discuss, report and hopefully fix lots of bugs If you are

### [sage-devel] [test by ...] byline in trac

Hello, recently we have started using [tested by ..] in trac. This seems to have lead to some misunderstanding, see http://www.sagetrac.org/sage_trac/ticket/910 [but I have fixed that now, see check out the log toward the end] The idea behind [tested by ...] is not that the original author of

### [sage-devel] potential cause for #557: cython missing dictionary deallocation

Hello, for every module Cython generates runtime support code that is place at the end of the converted file. Each one of those has an __Pyx_Import function that gets called from PyMODINIT_FUNC init$MODULENAME(void) static PyObject *__Pyx_Import(PyObject *name, PyObject *from_list) {

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

the obvious person to implement this, Pretty much 100% what I just claimed in IRC, but cwitty might look at it during Bug Day 4. I'll see if I can find the time to do so soon. Let's hope so. - Robert Cheers, Michael On Oct 17, 2007, at 9:04 PM, mabshoff wrote: Hello, for every module

### [sage-devel] Re: sage-2.8.8 release

On Oct 19, 10:34 pm, William Stein [EMAIL PROTECTED] wrote: Hi, I'm planning to release sage-2.8.8 sometime tonight. I'll start working on it at about 4pm my time. I'll be on #sage-devel irc, in case you want to help out. http://trac.sagemath.org/sage_trac/milestone/sage-2.8.8 You

### [sage-devel] Re: zombies attack sage.math!

On Oct 19, 5:13 pm, [EMAIL PROTECTED] wrote: Ok... this isn't an early haloween scare. Hi boothby, There are two lisp.run processes taking up 100% processor, attached to the users jen and jacobml. Those are the only processes under those users, so I'm thinking they shouldn't be there.

### [sage-devel] Rules for closing tickets in trac

Hello, since this has come up repeatedly I would like to clarify: Do not close any tickets in trac unless you have been explicitly told to do so by either malb, was, cwitty or mabshoff. This is to avoid having issues slip through the cracks. Once a ticket is closed and off the top of the time

### [sage-devel] Re: Rules for closing tickets in trac

On Oct 22, 10:40 am, Martin Albrecht [EMAIL PROTECTED] wrote: On Monday 22 October 2007, mabshoff wrote: Hello, Hello, since this has come up repeatedly I would like to clarify: Do not close any tickets in trac unless you have been explicitly told to do so by either malb

### [sage-devel] Re: Rules for closing tickets in trac

On Oct 22, 11:13 am, Martin Albrecht [EMAIL PROTECTED] wrote: Take ticket 729 as an example (http://trac.sagemath.org/sage_trac/ticket/729):It was closed by Robert (rml) because the bugfix/feature request was invalid. Michael (mabshoff) reopened it due to the rule state above

### [sage-devel] Re: Rules for closing tickets in trac

On Oct 22, 5:17 pm, Robert Miller [EMAIL PROTECTED] wrote: What caused me to actually raise the issue is #656: That one is clearly not a duplicate. #968 is an enhancement relative to #656. During Bug Day 4 William also told rlm not to close tickets until the issue had been officially

### [sage-devel] Re: 2.8.8.1 on Ubuntu

On Oct 22, 6:52 pm, John Voight [EMAIL PROTECTED] wrote: Hi all, I did a fresh install of Ubuntu, downloaded 2.8.7, then did a sage - upgrade, and got the following error: [EMAIL PROTECTED]:/home/kostadm/sage# ./sage -upgrade [...] GCC Version gcc -v Using built-in specs. Target:

### [sage-devel] Re: problem with showing plots from command line

On Oct 23, 8:20 am, Jonathan Bober [EMAIL PROTECTED] wrote: Hi folks. Hello Jonathan, I tried to send the following email a few hours ago (but I put the email address in wrong) and I don't feel like rewriting it all. So I should add to it now that I have upgraded sage (so I am running

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

On Oct 23, 1:23 pm, Jaap Spies [EMAIL PROTECTED] wrote: Last year after less than two days I could finish a calculation and write to William: Original Message Subject: dance(10) Date: Thu, 09 Mar 2006 00:10:19 +0100 From: Jaap Spies [EMAIL PROTECTED] To: William

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

On Oct 24, 12:31 pm, Jaap Spies [EMAIL PROTECTED] wrote: Michael, Hello Jaap, You wrote: dance(10) computes fine on sage.math (in about 6 hours under gdb), I am running dance(11) to see if it finishes [I guess you would like the result ;)]. Yes, sure! Ok, should it finish I will

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

On Oct 24, 6:52 pm, Jaap Spies [EMAIL PROTECTED] wrote: mabshoff wrote: On Oct 24, 6:27 pm, William Stein [EMAIL PROTECTED] wrote: On 10/24/07, Jaap Spies [EMAIL PROTECTED] wrote: I am on that, I got a 32 bit build of 2.8.9.alpha0. By the way, could you remind me where dance

### [sage-devel] Re: edit_module patch updated

On Oct 24, 6:50 pm, William Stein [EMAIL PROTECTED] wrote: On 10/24/07, Nils Bruin [EMAIL PROTECTED] wrote: I understand that the bg= hack is a quick way of getting the configurability you want, but frankly, I would find it hard to explain the existence of that option independent of the

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 24, 9:01 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: Robert, I've implemented a function and hook to do this in the new version of Cython, Cool. but I'm not sure how well it will work in practice on the entire SAGE library. It will decref local variable and all, but then if

### [sage-devel] Re: Notices this month

On Oct 24, 8:44 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: Hello, I've noticed sometimes the public sage notebook is really, really slow, for instance when someone is running a lot of dsage or valgrind jobs. since you mention valgrind I would like to remark that I usually limit myself

### [sage-devel] sloccount of sage-2.8.9.rc1

Hello, I ran sloccount on the latest rc1 and here are the results: SLOCDirectory SLOC-by-Language (Sorted) 687172 python-2.5.1.p7 ansic=354375,python=315376,asm=6567,sh=3895,lisp=3683, perl=2520,objc=756 422885 scipy-20070817

### [sage-devel] Re: sloccount of sage-2.8.9.rc1

Sorry to reply to myself so quickly, but as Carl Witty pointed out I need to run the code with --multiproject. In addition we now count pxd, pxi and pyx as python. With those settings we do get slighly smaller number, but still very impressive results: SLOCDirectory SLOC-by-Language

### [sage-devel] Re: SAGE 2.8.9rc1

So far four issues have popped up: 1) sage-banner is zero bytes in size 2) On x86 linux we have the following failure: [EMAIL PROTECTED] sage-2.8.9.rc1]$ ./sage -t devel/sage-main/sage/ rings/polynomial/multi_polynomial_ideal.py sage -t devel/sage-main/sage/rings/polynomial/

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 25, 9:06 am, Robert Bradshaw [EMAIL PROTECTED] wrote: Hi Robert, Seehttp://sage.math.washington.edu/home/robertwb/cython/All tests pass with cleanup level 1 (now default). The command line option --cleanup n sets the level (0 = n = 3). Things crash on quit (in SAGE, though not

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

On Oct 24, 7:00 pm, William Stein [EMAIL PROTECTED] wrote: On 10/24/07, Jaap Spies [EMAIL PROTECTED] wrote: It is not in matrix2.pyx, It is on the bottom of my first message and here below. It uses some functions/methods present in matrix2.pyx: rook_vector, permanental_minor,

### [sage-devel] Re: trac ticket #1000?

On Oct 25, 2:48 pm, David Harvey [EMAIL PROTECTED] wrote: Does the lucky bug reporter get a prize? He/she will be allowed to fix it ;) - if that isn't price enough I don't know what would be *ducks* Two more tickets :) david Cheers, Michael

### [sage-devel] Re: sloccount of sage-2.8.9.rc1

On Oct 25, 6:14 pm, David Joyner [EMAIL PROTECTED] wrote: On 10/25/07, William Stein [EMAIL PROTECTED] wrote: Hello, On 10/25/07, Bill Hart [EMAIL PROTECTED] wrote: There are some real surprises on that list. MPFR has many more lines of code than I thought, Pari many fewer lines

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 25, 11:25 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Oct 25, 9:06 am, Robert Bradshaw [EMAIL PROTECTED] wrote: Hi Robert, Seehttp://sage.math.washington.edu/home/robertwb/cython/Alltests pass with cleanup level 1 (now default). The command line option --cleanup n

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 25, 8:04 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 25, 2007, at 10:03 AM, mabshoff wrote: On Oct 25, 11:25 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Oct 25, 9:06 am, Robert Bradshaw [EMAIL PROTECTED] wrote: Hi Robert, Seehttp

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 25, 9:34 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 25, 2007, at 12:14 PM, mabshoff wrote: On Oct 25, 8:04 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 25, 2007, at 10:03 AM, mabshoff wrote: On Oct 25, 11:25 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 26, 5:18 am, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 25, 2007, at 7:46 PM, mabshoff wrote: On Oct 25, 9:34 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: Hi Robert, Try adding --clean 2 to line 1008 of process_cython_file() in setup.py. that doesn't work yet

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

Hello Jaap, I assume you care about the following (computed on sage.math): sage: dance(11) h^11 - 44*h^10 + 1045*h^9 - 16500*h^8 + 187935*h^7 - 1595748*h^6 + 10199343*h^5 - 48691500*h^4 + 169140180*h^3 - 405230320*h^2 + 600311624*h - 415232800 I am currently computing dance(12) on sage.math.

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

On Oct 27, 1:57 am, Jaap Spies [EMAIL PROTECTED] wrote: Jaap Spies wrote: Hello Jaap, Actually I'm running dance(10) now on my machine and I hope there will be no segfaults, because I simplified the code. It will take less than 3.5 hours to finish. Sorry, my hope was idle: same

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

On Oct 27, 1:48 pm, Jaap Spies [EMAIL PROTECTED] wrote: Hi Michael, You wrote: On a side note: Could you comment on #217? It is rather vague and there have been some improvements. If you have more improvements relative to #931 you should open another/more tickets for it/them. Now you

### [sage-devel] Re: Fun Things to do with a Sage Notebook

On Oct 27, 8:13 pm, TrixB4Kidz [EMAIL PROTECTED] wrote: Hello Brian, Here are a few fun things that anyone can do with a public Sage Notebook: 1. Use the Sage server as remote file storage. Take your pick between ftp, cvs, subversion, or even brew your own protocol. 2. Host your own

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 27, 1:26 am, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 25, 2007, at 9:35 PM, mabshoff wrote: Carl Witty was also wondering whether your newCython.spkg was ready for 2.8.10 or if we should wait. I believe so, it compiles all of SAGE and passes all doctests. Stefan

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

Okay, I got some new results: Changing permanent() slightly in matrix2.pyx: print entering permanent() - m: ,m, n: ,n from sage.rings.arith import binomial for r from 1 = r m+1: lst = _choose(n, r) print lst, lst tmp = []

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 28, 9:48 am, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 28, 2007, at 1:29 AM, mabshoff wrote: Hi Robert, For 2.8.10.alpha1+Craig's fix and python compiled using --without- pymalloc I get with the default cleanup level 1: ==6569== LEAK SUMMARY: ==6569==definitely

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 28, 10:33 am, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 28, 2007, at 2:17 AM, mabshoff wrote: Hi Robert, On Oct 28, 9:48 am, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 28, 2007, at 1:29 AM, mabshoff wrote: Hi Robert, For 2.8.10.alpha1+Craig's fix and python

### [sage-devel] Re: potential cause for #557: cython missing dictionary deallocation

On Oct 28, 11:26 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Oct 28, 10:33 am, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 28, 2007, at 2:17 AM, mabshoff wrote: Hi Robert, On Oct 28, 9:48 am, Robert Bradshaw [EMAIL PROTECTED] wrote: On Oct 28, 2007, at 1:29 AM

### [sage-devel] Re: LiDIA

repo for LiDIA a couple of weeks ago. [23:25] mabshoff Jep, I figured you were the right guy to do that in person :) [23:25] rpw further details on sage-devel (ml) tomorrow morning. [23:25] mabshoff mk [23:25] rpw I'm to tired to type straight atm. I've been awake too long. [23:26] rpw see you guys

### [sage-devel] Announcement for Sage Bug Day 5: November 3rd, 10am PST

Hello folks, Bug Day 5 is now planned for Saturday, November 3rd, 2007. Official start will be 10am PST, but as usual people from European time zones or the east coast might start earlier and finish a little sooner. I you would like to participate add your name to the list at

### [sage-devel] Re: Sage 2.8.10 is released

On Oct 29, 7:13 am, William Stein [EMAIL PROTECTED] wrote: On 10/28/07, Carl Witty [EMAIL PROTECTED] wrote: Sage 2.8.10 has been released. Download from http://sagemath.org/download.htmlor upgrade with sage -upgrade, as usual. This release includes updated spkg's prepared by Robert

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

I did look into this some more and I did verify that the refcounts wraps: lst [[0, 1, 2, 3, 4, 5, 6]] lst [[0], [1], [2], [3], [4], [5], [6]] lst [[0, 1], [0, 2], [1, 2], [0, 3], [1, 3], [2, 3], [0, 4], [1, 4], [2, 4], [3, 4], [0, 5], [1, 5], [2, 5], [3, 5], [4, 5], [0, 6], [1, 6], [2, 6], [3,

### [sage-devel] Re: SAGE on Leopard

On Oct 30, 1:24 am, Justin Walker [EMAIL PROTECTED] wrote: Hi Justin, I figured I'd give this a try. The first to go is 'flint', with this error: g++ -single_module -fPIC -dynamiclib -o libflint.dylib mpn_extras.o Z.o memory-\ manager.o Z_mpn.o ZmodF.o ZmodF_mul.o ZmodF_mul-tuning.o

### [sage-devel] Re: SAGE on Leopard

On Oct 30, 3:34 am, Jason Martin [EMAIL PROTECTED] wrote: Has anyone tried a 64-bit build on Leopard? I just picked up Leopard today, so I'll hopefully have a running Leopard machine tomorrow on which to start playing. Just wondering if, for example, python can build in 64-bit mode on

### [sage-devel] Re: Integrating SymPy with SAGE

On Oct 30, 3:07 am, Ondrej Certik [EMAIL PROTECTED] wrote: We made a new release of SymPy with those _sage_() methods so that it can be integrated in SAGE more systematically. If some suggestions arise now, we'll simply change it and release again. Ondrej Hello Ondrej, just link the new

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

memleaks. Thanks and good luck, Carl had some interesting input: [02:03] cwitty I was looking at those refcounts some more. [02:03] mabshoff ok [02:03] cwitty It turns out that Python caches and shares small int objects: [02:04] cwitty sage: a = int(0) [02:04] cwitty sage: sys.getrefcount(a) [02:04

### [sage-devel] Re: Py_ssize_t question

On Oct 31, 3:11 am, Carl Witty [EMAIL PROTECTED] wrote: On Oct 29, 10:11 am, Robert Bradshaw [EMAIL PROTECTED] wrote: Hello, There is another way that Py_ssize_t differs from int, namely that Cython casting happens via the __index__ rather than __int__ function. __int__ is

### [sage-devel] Re: Unhandled SIGSEGV: Ticket #973

at least some of the earlier versions] which Carl tracked down after I isolated the cause: [02:30] mabshoff Ok, every time c=0 the refcount for int(0) goes up by one. [02:42] cwitty It's a Cython bug. [02:42] mabshoff Yep, for c in cols: [02:42] mabshoff increments the refcount on int(?) [02:42] cwitty

### [sage-devel] optional spkgs that should be pushed into the repo

Hello, there are two optional spkg in trac against 2.8.11. I cannot up them myself, so I would like William to get those into the optional spkg repo. Those two are: #705[with spkg] Make vtk an easy-to-install optional sage package #1033 [with optional spkg] biopython 1.44 optional package

### [sage-devel] Re: policy on new trac tickets

On Oct 31, 1:50 pm, Ondrej Certik [EMAIL PROTECTED] wrote: Hi, Hello Ondrej, when I have one particular feature to discuss, should I discuss it here, or open a new trac ticket for that? Something this controversial should be discussed here first. Either way you should get a trac account

### [sage-devel] Re: Py_ssize_t question

On Oct 31, 9:55 pm, Jaap Spies [EMAIL PROTECTED] wrote: Hi Michael, it should also be noted that the bug Carl mention above seems to be the root cause for #973. I am currently updating to 2.8.10 on my local box (which shows the segfault for dance(10)) to see if the problem is really

### [sage-devel] 2.8.11.alpha0 released

I have released 2.8.11.alpha0 at http://sage.math.washington.edu/home/mabshoff/sage-2.8.11.alpha0.tar It passes testall on sage.math, but I would like to get some build feedback on OSX 10.4, both PPC and Intel flavors, as well as 32 bit Linux. I plan to release 2.8.11 final by late Friday night

### [sage-devel] 2.8.11.rc1 released

I have released 2.8.11.rc1 (sorry, I skipped rc0, by the time I realized the problem I had already called it rc1 in trac) at http://sage.math.washington.edu/home/mabshoff/sage-2.8.11.rc1.tar It passes testall on sage.math, but I would like to get some build feedback on OSX 10.4, both PPC

### [sage-devel] Re: Announcement for Sage Bug Day 5: November 3rd, 10am PST

On Oct 29, 6:13 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: Hello folks, BugDay5 is now planned for Saturday, November 3rd, 2007. Official start will be 10am PST, but as usual people from European time zones or the east coast might start earlier and finish a little sooner. I you

### [sage-devel] Re: 2.8.11.rc1 released

On Nov 2, 5:29 am, [EMAIL PROTECTED] wrote: Hello boothby, The expected output is incorrect; the actual output is correct. Okay, I am fixing the doctest then. We are planning an rc2 in a couple hours if William and I get it to compile on 10.5 without the need for manual interaction. We are

### [sage-devel] Re: 2.8.11.rc1 released

On Nov 2, 12:45 pm, Joel B. Mohler [EMAIL PROTECTED] wrote: On Friday 02 November 2007 00:17, mabshoff wrote: #1032: Latex'ing variable names is more robust and consistent (Joel Mohler) - this one was actually backed out again - see the ticket for comment It's possible that I'm

### [sage-devel] Re: libPng.dylib

On Nov 2, 6:33 pm, William Stein [EMAIL PROTECTED] wrote: On Fri, 02 Nov 2007 10:26:13 -0700, Justin C. Walker [EMAIL PROTECTED] wrote: Well, it also hits us on Linux, so I still think it should happen. malb's problem with firefox is just one example where that happened and he just

### [sage-devel] Re: 2.8.11.rc1 released

A short outlook: People on OpenSuSE 10.2 should know the following: [09:33] Syzygy- Hmph. I cannot get yast to tell me what the g77- package is named. *grmbl* [09:33] mabshoff Which SuSE release? [09:34] mabshoff You should probably install gfortran [09:34] mabshoff 10.3 no longer ships g77

### [sage-devel] Re: numpy vs. in-place optimizations

On Nov 2, 8:25 pm, William Stein [EMAIL PROTECTED] wrote: On 11/2/07, Carl Witty [EMAIL PROTECTED] wrote: On Nov 2, 11:25 am, Robert Bradshaw [EMAIL PROTECTED] wrote: :-(, but I have to concede to your logic. The line to change is 148 of coerce.pxi. Setting this value to 0 will

### [sage-devel] Re: 2.8.11.rc1 released

On Nov 2, 7:39 pm, Joel B. Mohler [EMAIL PROTECTED] wrote: On Friday 02 November 2007 10:45, mabshoff wrote: On Nov 2, 12:45 pm, Joel B. Mohler [EMAIL PROTECTED] wrote: Everything is possible, but I am fairly sure that the behavior of the doctests only changes if the patch made

### [sage-devel] Re: 2.8.11.rc1 released

On Nov 3, 12:46 am, Joel B. Mohler [EMAIL PROTECTED] wrote: On Friday 02 November 2007 15:38, mabshoff wrote: The patch applied against rc1 passes with flying colors. You need to use the second bundle on the ticket since the first bundle is already in (but backed out). Maybe

### [sage-devel] Sage 2.8.11 Release Announcement

set (Carl Witty) Build instruction for OSX 10.4 It seems that a workaround introduced for OSX 10.5 causes a compile failure in LinBox. So if you are on OSX please try installing the following Givaro.spkg: http://sage.math.washington.edu/home/mabshoff/givaro-3.2.6.p2.spkg William is off

### [sage-devel] Re: Fwd: 10.5 issue?

On Nov 4, 5:05 am, William Stein [EMAIL PROTECTED] wrote: Hello, not at all for me. - William rpw tried building Sage on 10.5 with MACOSX_DEPLOYMENT_TARGET set to 10.4 so that we can build one binary that runs on both 10.4 and 10.5, but he got some error message that indicates that maybe

### [sage-devel] Sage 2.8.12.alpha1 and release plan

Hello folks, you can find 2.8.12.alpha1 at http://sage.math.washington.edu/home/mabshoff/sage-2.8.12.alpha1.tar alpha1 is the result of the bug fixes merged by William during Bug Day 5 as well as two minor spkg updates. There is currently onc doctest failure in schemes/elliptic_curves

### [sage-devel] Re: dense F_p matrix multiplication

On Nov 5, 2:10 pm, William Stein [EMAIL PROTECTED] wrote: On 11/5/07, Martin Albrecht [EMAIL PROTECTED] wrote: Hello, I've got a naive question: Why isn't linbox the default choice for matrix multiplication over F_p? (1) It was probably broken when we first wrapped matrix multiply

### [sage-devel] Re: dense F_p matrix multiplication

On Nov 5, 3:01 pm, William Stein [EMAIL PROTECTED] wrote: On 11/5/07, Martin Albrecht [EMAIL PROTECTED] wrote: Hi, this is probably due to the faster BLAS implementation on my notebook (and the standard GSL on your's). So we could remember which BLAS we use and default to LinBox

### [sage-devel] Re: dense F_p matrix multiplication

On Nov 5, 3:12 pm, John Cremona [EMAIL PROTECTED] wrote: It would be nice if it were documented somewhere how big the optional packages are (e.g. file sizes displayed athttp://www.sagemath.org/packages/optional/) ...waiting for atlas to download... and now seeing the error message

### [sage-devel] Re: dense F_p matrix multiplication

Hi John, On Nov 5, 3:45 pm, John Cremona [EMAIL PROTECTED] wrote: After installing Atlas (took 20 minutes) it runs more slowly! sage: sage: %time C = A._multiply_linbox(B) CPU times: user 72.32 s, sys: 1.02 s, total: 73.34 s Wall time: 80.09 On sage.math time drops from 11.86s to 10.83,

### [sage-devel] Re: dense F_p matrix multiplication

On Nov 5, 3:57 pm, William Stein [EMAIL PROTECTED] wrote: On 11/5/07, John Cremona [EMAIL PROTECTED] wrote: After installing Atlas (took 20 minutes) it runs more slowly! No, it will run at exactly the same speed. You also have to rebuild linbox in such a way that it actually takes

### [sage-devel] Re: dense F_p matrix multiplication

On Nov 5, 5:24 pm, William Stein [EMAIL PROTECTED] wrote: On 11/5/07, mabshoff [EMAIL PROTECTED] wrote: Ignore my last email, I forgot to rebuild LinBox. I am surprised how much timings vary I get from running matrix matrix multiplies, especially since sage.math is not loaded

### [sage-devel] Re: dense F_p matrix multiplication

it to satisfy the linker, no actual static or dynamic library actually ends up getting used. Just compared the size and linked libraries of William's plain LinBox with cblas vs. my optimized with ATLAS: [EMAIL PROTECTED]:/tmp/Work-mabshoff/sage-2.8.11$ ls -al /home/was/s/local/ lib/liblinboxwrap.so

### [sage-devel] Re: MACOSX_DEPLOYMENT_TARGET (binaries working on both OSX 10.4 and 10.5)

On Nov 5, 10:51 pm, Ralf-Philipp Weinmann [EMAIL PROTECTED] darmstadt.de wrote: Hello list, Hello Ralf, I've finished building and testing SAGE 2.8.11 (on ppc) MACOSX_DEPLOYMENT_TARGET=10.3 This causes a build produced on OSX 10.5 to _almost_ work on 10.4. The culprit that forces me

### [sage-devel] Re: Sage 2.8.12.alpha1 and release plan

Since William just asked me here an update: real work kept me busy all day, now I am merging patches. The plan is: If you have any objects please let me know now! Will go in #683, #989: Stripping $ from documentation #995: Generalize polynomial .roots() method by adding optional ring=

### [sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

as widely tested as other components of Sage. This is now trac #1126: Kate, could you try http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p0.spkg and report back it that solves the issue? Cheers, Michael http://trac.sagemath.org/sage_trac/ticket/1126 I've made both trac

### [sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

On Nov 8, 3:59 pm, Kate [EMAIL PROTECTED] wrote: Michael, Hello Kate, I have tried http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p... and can report that it builds on my x86_64-Linux box. Great. I will make sure the updated spkg goes into 2.9 or whatever

### [sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

On Nov 8, 9:50 pm, Kate [EMAIL PROTECTED] wrote: Michael, SNIP sage -t devel/sage-main/sage/numerical/test.py ** File test.py, line 4: : from cvxopt.base import * Exception raised: Traceback (most recent call

### [sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

On Nov 8, 9:50 pm, Kate [EMAIL PROTECTED] wrote: Michael, Kate, Much thanks for the link to Josh's update of cvxopt.spkg. No problem. With that fix, I now can compile on all the architectures I am currently interested in: x86-Linux, x86_64-Linux, and ia64-Linux. The next step is to

### [sage-devel] Re: number_field_element coercion

On Nov 8, 10:46 pm, John Voight [EMAIL PROTECTED] wrote: Hello all, Hi John, Check this out: sage: def stupid_function(n): : Z_F = NumberField(x^2-x-1, 't').maximal_order() : for i in range(n): : Z_F([5,1]) : sage: prun stupid_function(10^4)

### [sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

). Nope, I agree that this is not a solution. And we do add $SAGE_LOCAL/ lib to LD_LIBRARY_PATH which causes the problem in the first place. Thoughts? :) Off to the airport Josh Michael On Nov 8, 1:11 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 8, 9:50 pm, Kate [EMAIL

### [sage-devel] 2.8.13 and 2.9 release plans

Greeting from Sage Days 6 in Bristol, after a short discussion we would like to make the following release plans: - 2.8.13 on Nov. 18th, 2007 which should be another small bugfix and feature release. - 2.9 on Nov. 25th, 2007 with hopefully ATLAS support and potential 64 bit OSX support as well

### [sage-devel] Re: gdb, doctests, strange behavior...

On Nov 12, 9:20 am, William Stein [EMAIL PROTECTED] wrote: On Mon, 12 Nov 2007 06:47:06 -, Robert Miller [EMAIL PROTECTED] wrote: (1) Do you or do you not actually have the same problem when you build the same code under Linux? You don't say above. Hello, I hadn't had the

### [sage-devel] Re: plotQt.c with Qt 4.3.2 + GUI for pari/gp

On Nov 13, 12:41 pm, David Joyner [EMAIL PROTECTED] wrote: On 11/13/07, Fabio Tonti [EMAIL PROTECTED] wrote: The original Webpage says [mathGUIde] ist Freeware und wird mit allen Quellen verbreitet which means that it's freeware and is distributed with all the sources. So it doesn't

### [sage-devel] Re: plotQt.c with Qt 4.3.2 + GUI for pari/gp

On Nov 13, 6:08 pm, mhampton [EMAIL PROTECTED] wrote: To really compete with programs like mathematica or matlab, I think sage needs to be able to have interactive applet-like interfaces (e.g. like mathematica's Manipulate). It seems possible and probably most desirable to do this with

### [sage-devel] Re: 2.8.13 and 2.9 release plans

On Nov 10, 11:47 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: Greeting from Sage Days 6 in Bristol, after a short discussion we would like to make the following release plans: -2.8.13on Nov. 18th, 2007 which should be another small bugfix and feature release. - 2.9 on Nov. 25th

### [sage-devel] Re: Error building sage in Solaris 10 with gcc 4.0.2

On Nov 14, 3:59 pm, David Joyner [EMAIL PROTECTED] wrote: Klas: Thanks for your report but it was sent to the wrong list. (The sf list is closed. I'm forwarding this to the correct list.) :) - David Joyner On Nov 14, 2007 8:19 AM, Klas Heggemann [EMAIL PROTECTED] wrote: This fails

### [sage-devel] Re: another sage talk...

On Nov 14, 2:59 pm, William Stein [EMAIL PROTECTED] wrote: http://sagemath.org/talks/20071114-sage_bristol/ -- William Stein Associate Professor of Mathematics University of Washingtonhttp://wstein.org And a direct link to the inquirer story:

### [sage-devel] More potential GPL issues with Singular

Searching some debian mailing lists I came across: Re: Advice on packaging SAGE - see http://lists.debian.org/debian-mentors/2007/06/threads.html Specifically from http://lists.debian.org/debian-mentors/2007/06/msg00020.html

### [sage-devel] klogd touble on sage.math

Hello, the disc subsystem seems slow on sage.math and behold: 28099 messageb 25 0 2640 400 312 R 100 0.0 7656:04 klogd i.e. klogd is going nuts using 100% CPU on one core. Can somebody with appropriate rights investigate this? klogd has been started -P which I do not know and isn't

### [sage-devel] Re: Coercion trouble

then. I was also wondering if you ever opened a ticket about the --rpath issue that caused compilation failure on OSX when moving the install. I can't find it, so if you don't want to open that one let me know and I will do. Cheers, Michael On Nov 15, 2007 8:57 PM, mabshoff [EMAIL PROTECTED

### [sage-devel] Bug Day 6 proposal: Sat. Nov. 24th. 2007

Hello, I would like to propose that the next Bug Day is held on Sat. Nov. 24th. 2007. That is the day before the planned 2.9 release. Since we want to have a point release as a basis for the Bug Day we might have to shift the releases around a little or alternatively this time work of a 2.9pre

### [sage-devel] Re: Coercion trouble

On Nov 16, 1:30 am, Iftikhar Burhanuddin [EMAIL PROTECTED] wrote: Hi folks, Hello Ifti, I run into some coercion trouble when I reduce a fourier coefficient of a cusp form modulo a prime ideal. (See below.) Any idea how I can avoid this? No clue for now, but that looks like a bug to

### [sage-devel] Re: Coercion trouble

On Nov 16, 3:43 am, David Roe [EMAIL PROTECTED] wrote: Hi David, I lost internet connection and then lost the traceback when my machine restarted, so if you could open a ticket on the __rpath issue, I would apprectiate it. The residue field problem is ticket 1183. David Yep, no

### [sage-devel] Re: SAGE marketing

On Nov 15, 9:18 pm, Ted Kosan [EMAIL PROTECTED] wrote: Who are the main people who are responsible for SAGE marketing? I will have some free time in December and I would like to devote some of it to helping with SAGE's marketing effort. Ted Hi Ted, I don't think there is a formal

### [sage-devel] Re: Bug Day 6 proposal: Sat. Nov. 24th. 2007

On Nov 16, 7:49 am, Nick Alexander [EMAIL PROTECTED] wrote: On 15-Nov-07, at 6:32 PM, mabshoff wrote: Hello, I would like to propose that the next Bug Day is held on Sat. Nov. 24th. 2007. That is the day before the planned 2.9 release. Since we want to have a point release as a basis