Re: [sage-devel] sage days: Leiden Poster

On Mon, 1 Mar 2010 22:03:07 -0800, William Stein wrote: > Does anybody have a picture they might like to be featured on the > poster for the upcoming Sage Days in Leiden, Netherlands? Do we have a more precise idea for the workshop's topics than "Number theory"? That might help restrict the pict

Re: [sage-devel] BipartiteGraph status

Sounds like a good summer of code project? LOOK ITS A SIGNATURE CLICK IF YOU DARE--- http://www.google.com/profiles/zitterbewegung On Fri, Feb 26, 2010 at 11:05 AM, Ryan Hinton wrote: > I'm having a lovely conversation with myself in the comments for trac > #8350 that I want to share. :

[sage-devel] Re: BipartiteGraph status

On 03/01/2010 04:45 PM, Ryan Hinton wrote: As for your "documentation" solution, I think this is where we disagree. If I use tab completion and find a method hanging on a BipartiteGraph instance, I expect it to work. In other words, if it is written, documented, and tested in generic_graph.py

Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???

On Mon, Mar 1, 2010 at 5:15 AM, Dr. David Kirkby wrote: > I've just been looking at the SPKG.txt for sqlite and see: > > > === sqlite-3.6.19.p0 (Mike Hansen, October 26th, 2009) === >  * Updated to 3.6.19 with > http://sqlite.org/sqlite-amalgamation-3.6.19.tar.gz. > > === sqlite-3.6.17.p0 (Dan Dra

[sage-devel] sage days: Leiden Poster

Hi, Does anybody have a picture they might like to be featured on the poster for the upcoming Sage Days in Leiden, Netherlands? -- William -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@goog

Re: [sage-devel] Re: Bipartite graphs in Sage

On Mon, Mar 1, 2010 at 9:57 AM, Ryan Hinton wrote: > Incidentally, this is my option (A).  I agree it is the cleanest > option.  (See my comments on the original thread, groups.google.com/group/sage-devel/browse_thread/thread/ > bff3af2a3c77b4b6>.) I had the impression taht Robert Miller has mad

[sage-devel] Re: Questions and proposals for matrices

On 03/01/2010 09:37 PM, Dima Pasechnik wrote: I guess, this: http://trac.sagemath.org/sage_trac/ticket/7723 "I have not idea when I can get back to this at the moment. Basically what has happened is that I bit the bullet and implemented my own numerical matrix class hierarchy which is usable with

[sage-devel] Re: Questions and proposals for matrices

I guess, this: http://trac.sagemath.org/sage_trac/ticket/7723 "I have not idea when I can get back to this at the moment. Basically what has happened is that I bit the bullet and implemented my own numerical matrix class hierarchy which is usable without Sage (but loosely modeled after it). That en

[sage-devel] Re: 0 < sqrt3 is False in QuadraticField

On Mar 2, 3:10 am, Robert Bradshaw wrote: > On Feb 28, 2010, at 4:20 PM, slabbe wrote: > > > Hi Sage-devel, > > > I am currently experiencing some problems when comparing elements of a > > QuadraticField. See below. > > > sage: Q. = QuadraticField(3) > > sage: 0 < sqrt3 > > False > > sage: RR(sq

[sage-devel] t2.math: friendly reminder to delete unnecessary files under /scratch

Hi folks, The machine t2.math has a fast-ish scratch area mounted at /scratch. However, note that that partition is very limited in size, around 25 GB total. At the moment, the partition is near capacity as shown by the following snippet from "df -h": [mv...@t2 ~]$ df -h Filesystem si

[sage-devel] Re: ALL doctests pass on Solaris !!!

hmm, there are sparc solaris machines on skynet; they are much faster than t2... On Mar 2, 2:29 am, Robert Bradshaw wrote: > On Mar 1, 2010, at 9:06 AM, Dr. David Kirkby wrote: > > > mhampton wrote: > >> Congratulations, it seems that you have made a great deal of progress > >> on this! > >> -Mar

[sage-devel] Re: Possible to avoid "sage:" in example code?

Thanks for the reply, John. This is exactly what I want, and what I am doing. The problem is for the code block to be a "cell" with an evaluate option at the end of it when viewing through the notebook server, I have to do this: --- """ stuff stuff :: sage: first line of code sage: secon

Re: [sage-devel] gsoc ideas list

Hi Minh, On Tue, 2 Mar 2010 10:52:44 +1100 Minh Nguyen wrote: > On Tue, Mar 2, 2010 at 8:36 AM, Burcin Erocal > wrote: > > > > > Since we're definitely applying as a mentoring organization, I > > suggest we put a link to the project list from the homepage to > > attract students. Harald, Min

Re: [sage-devel] gsoc ideas list

Hi Burcin, On Tue, Mar 2, 2010 at 8:36 AM, Burcin Erocal wrote: > Since we're definitely applying as a mentoring organization, I suggest > we put a link to the project list from the homepage to attract students. > Harald, Minh, could you take care of this? Your wish is my command :-) See the

Re: [sage-devel] Re: BipartiteGraph status

This will be my last post on the topic for now. On Mon, Mar 1, 2010 at 2:45 PM, Ryan Hinton wrote: > Again, the wishful thinking is the assumptions.  Here are a few > examples. > > * The copy() method calls the DiGraph and Graph constructors > directly.  To get all the same functionality (e.g. co

[sage-devel] GSOC - Sage benchmark ??

Some time back I proposed we had a Sage benchmark, based on one from Karl Unterkofler who has written a quite widely used benchmark for Mathematica http://trac.sagemath.org/sage_trac/ticket/6808 That there should not be hard, and would not form a major part of any project. But taking the idea

[sage-devel] Re: BipartiteGraph status

For the impatient, I'll give the summary here at the top. For what it's worth, my current opinion is that a mixture of options (B) and (C) are probably best. Given the backend abstraction, overriding the core public interface (add/delete_edge, add/ delete_vertex) will result in most methods worki

Re: [sage-devel] Questions and proposals for matrices

On Thu, Dec 17, 2009 at 6:07 AM, Dag Sverre Seljebotn wrote: > Patches up for a basic sparse fp matrix, #7723. That's the very basics, > and if accepted I can move on to the fancier stuff -- I prefer getting > corrections of course early... > > William Stein wrote: >> I really hope that the Sage m

Re: [sage-devel] Sanity check on objects, parents and elements

Hi Robert, >> One of the main problem here is that PEP 335 "Overloadable Boolean >> Operators" >> is not yet accepted. So right now there is no way to implement a three >> state >> logic, is there one ? If not, Is there a way we can push on python dev to >> have >> this PEP accepted ? >

Re: [sage-devel] Sanity check on objects, parents and elements

On Mar 1, 2010, at 1:22 PM, Florent Hivert wrote: Not my idea. This was the way it worked in MuPAD. There was a three state boolean value, which was quite useful. Looking into python docs to see if we can have "and" and "or" work with a 3-state booleans, I found: " A rich comparison method

Re: [sage-devel] gsoc ideas list

On Mon, 1 Mar 2010 13:54:03 +0900 Dan Drake wrote: > On Sun, 28 Feb 2010 at 09:02PM +0100, Burcin Erocal wrote: > > After the recent thread about Google Summer of Code [1], I set up a > > wiki page to collect project ideas: > > > > http://wiki.sagemath.org/gsoc10 > > > > [1] http://groups.goog

Re: [sage-devel] Sanity check on objects, parents and elements

>> Not my idea. This was the way it worked in MuPAD. There was a three state >> boolean value, which was quite useful. Looking into python docs to see if >> we >> can have "and" and "or" work with a 3-state booleans, I found: >> >> " A rich comparison method may return the singleton NotImplemented

Re: [sage-devel] Re: gsoc ideas list

On Mon, 01 Mar 2010 06:28:16 -0600 Jason Grout wrote: > On 02/28/2010 02:02 PM, Burcin Erocal wrote: > > Hi, > > > > After the recent thread about Google Summer of Code [1], I set up a > > wiki page to collect project ideas: > > > > http://wiki.sagemath.org/gsoc10 > > > > [1] http://groups.google

[sage-devel] Re: Failure building MPIR on sage 4.3.2

I tried the same exercise on a related Xeon cluster -- with the same failure on mpn/.libs/add_n.o. I will be on #sage-devel (IRC) off and on if anyone wants to work on this real-time. The (new) config.log is at . The behavior in both cases appears t

Re: [sage-devel] Re: BipartiteGraph status

+1 to Robert's arguments. Using class inheritance as much as you can is the way to go. David On Mon, Mar 1, 2010 at 3:18 PM, Robert Miller wrote: > A. Change BipartiteGraph so that it doesn't inherit from Graph. > > B. Make BipartiteGraph handling an integral part of the Graph class... > > C.

[sage-devel] Re: Possible to avoid "sage:" in example code?

On Mar 1, 8:22 am, tommct wrote: > I am using Sphinx to document my package. If I place the resulting > html in my SAGE notebook server, I get a nice, interactive reference, > but only when each line in my code examples are prefixed with "sage:" > or ">>>". I would like my chunks of example code t

Re: [sage-devel] Re: BipartiteGraph status

A. Change BipartiteGraph so that it doesn't inherit from Graph. B. Make BipartiteGraph handling an integral part of the Graph class... C. ... BipartiteGraph is a subclass of Graph and overrides methods when necessary. On Mon, Mar 1, 2010 at 9:55 AM, Ryan Hinton wrote: > It looks like you're a

Re: [sage-devel] Re: What is the default for SAGE_TIMEOUT_LONG ?

John H Palmieri wrote: On Mar 1, 9:38 am, "Dr. David Kirkby" wrote: Given one test took 460 s on my 10-year old Sun, I suspect I need to increase SAGE_TIMEOUT_LONG if I run the long tests. What is the default value? The default value is 1800 seconds. It's defined in SAGE_ROOT/local/ bin/sage

Re: [sage-devel] Sanity check on objects, parents and elements

On Feb 27, 2010, at 2:22 PM, Florent Hivert wrote: Hi Robert, You get the point. As far as I understand a RIF only return True if the interval are reduced to a single point. Is it right ? It would be better to return a special value like Unknown than False. But that's another question

Re: [sage-devel] 0 < sqrt3 is False in QuadraticField

On Feb 28, 2010, at 4:20 PM, slabbe wrote: Hi Sage-devel, I am currently experiencing some problems when comparing elements of a QuadraticField. See below. sage: Q. = QuadraticField(3) sage: 0 < sqrt3 False sage: RR(sqrt3) 1.73205080756888 [...] Is this known? Yes, cmp() for number field

Re: [sage-devel] Re: ALL doctests pass on Solaris !!!

Robert Bradshaw wrote: Once OpenSolaris is up and running, we could put it in a VM on boxen, and use it as part of the build farm. Of course that won't be a true Sparc solaris machine, but unless someone has extra money/hardware laying around it'll probably be a more realistic solution that wa

Re: [sage-devel] Re: GSOC

On Mar 1, 2010, at 4:48 AM, Dr. David Kirkby wrote: William Stein wrote: Yes, I think there should be a Sage GSOC application. I'm OK with being listed as a mentor. However, I won't write the actual application, since I wrote three applications in a row that were all turned down, so clearly

Re: [sage-devel] Re: ALL doctests pass on Solaris !!!

On Mar 1, 2010, at 9:06 AM, Dr. David Kirkby wrote: mhampton wrote: Congratulations, it seems that you have made a great deal of progress on this! -Marshall Yes, congratulations! Thank you Marshall. Hopefully, Solaris can soon become "fully supported" if all tests are passing. As long

[sage-devel] Re: What is the default for SAGE_TIMEOUT_LONG ?

On Mar 1, 9:38 am, "Dr. David Kirkby" wrote: > Given one test took 460 s on my 10-year old Sun, I suspect I need to increase > SAGE_TIMEOUT_LONG if I run the long tests. What is the default value? The default value is 1800 seconds. It's defined in SAGE_ROOT/local/ bin/sage-doctest: TIMEOUT_LONG

[sage-devel] Re: Bipartite graphs in Sage

Incidentally, this is my option (A). I agree it is the cleanest option. (See my comments on the original thread, .) - Ryan On Feb 27, 1:45 pm, Robert Bradshaw wrote: > Perhaps the correct thing to do is have BipartiteGraph wrap a Graph   > rather than descend from it. This way at least one wou

[sage-devel] Re: BipartiteGraph status

On Feb 26, 8:03 pm, Robert Miller wrote: > On Fri, Feb 26, 2010 at 9:05 AM, Ryan Hinton wrote: > > ... > > > OK, assume we solve (1) by requiring an indication of which partition > > a vertex belongs in and raising an exception otherwise.  What about > > Graph algorithms that change the graph tem

[sage-devel] Re: release manager for Sage 4.3.4

Hi Sébastien, On Tue, Mar 2, 2010 at 4:05 AM, slabbe wrote: > When do you expect 4.3.4 to be out? I'm aiming for roughly a 3 week schedule as follows: * Release Sage 4.3.4.alpha0 in the next few days. * Release Sage 4.3.4.alpha1 a week after the release of Sage 4.3.4.alpha0. * Release Sage 4

[sage-devel] What is the default for SAGE_TIMEOUT_LONG ?

Given one test took 460 s on my 10-year old Sun, I suspect I need to increase SAGE_TIMEOUT_LONG if I run the long tests. What is the default value? Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr..

Re: [sage-devel] Re: ALL doctests pass on Solaris !!!

mhampton wrote: Congratulations, it seems that you have made a great deal of progress on this! -Marshall Thank you Marshall. Hopefully, Solaris can soon become "fully supported" if all tests are passing. As long as the releases are handled carefully, and code not committed that breaks on So

[sage-devel] Re: BipartiteGraph status

Thanks for pointing to the new thread. :-) Yes, the same problem exists for add_edge(). At a minimum, and add/ delete vertex and add edge code needs to be overridden for BipartiteGraph. I've done the delete vertex and can do the others, but I wanted to clear up the "long-term" approach first.

[sage-devel] Possible to avoid "sage:" in example code?

I am using Sphinx to document my package. If I place the resulting html in my SAGE notebook server, I get a nice, interactive reference, but only when each line in my code examples are prefixed with "sage:" or ">>>". I would like my chunks of example code to exist in my Python modules, simply embed

[sage-devel] Summary of all patches need for Solaris.

I've created a ticket http://trac.sagemath.org/sage_trac/ticket/8409 that list all the patches need for Sage on Solaris. It is broken into two groups 1) Those needed for the build to succeed. 2) Those needed for all doc tests to pass. With a bit of care, 4.3.4 should build and pass all tests,

[sage-devel] Re: release manager for Sage 4.3.4

Hi folks, On Sun, Feb 28, 2010 at 8:00 PM, Minh Nguyen wrote: > Hi folks, > > Who wants to be release manager for Sage 4.3.4? I'm rather burnt out > after doing two releases in a row. I'm willing to team up with anyone who is interested in helping out with release management. If you're a beginne

[sage-devel] Re: ALL doctests pass on Solaris !!!

Congratulations, it seems that you have made a great deal of progress on this! -Marshall On Mar 1, 8:42 am, "Dr. David Kirkby" wrote: > I've just succeeded in getting all doctests to pass on Solaris. After updating > sqlite, which awaits review at: > > http://trac.sagemath.org/sage_trac/ticket/8

Re: [sage-devel] Solaris patches - please review to Sage working again.

Minh Nguyen wrote: Hi David, I have produced a source tarball that incorporates the patches and/or spkg's at the following tickets: * #7867 * #8391 * #8363 * #8374 * #8375 These patches and spkg's are applied on top of Sage 4.3.3. The build is still going on these machines: * sage.math * bsd.

Re: [sage-devel] ALL doctests pass on Solaris !!!

Dr. David Kirkby wrote: I've just succeeded in getting all doctests to pass on Solaris. After updating sqlite, which awaits review at: http://trac.sagemath.org/sage_trac/ticket/8408 as well as the following (some need review) * #7867 Python patch, to allow Sage library to build. * #81

[sage-devel] ALL doctests pass on Solaris !!!

I've just succeeded in getting all doctests to pass on Solaris. After updating sqlite, which awaits review at: http://trac.sagemath.org/sage_trac/ticket/8408 as well as the following (some need review) * #7867 Python patch, to allow Sage library to build. * #8191 Addition of iconv, whi

Re: [sage-devel] Solaris patches - please review to Sage working again.

Minh Nguyen wrote: Hi David, I have produced a source tarball that incorporates the patches and/or spkg's at the following tickets: * #7867 * #8391 * #8363 * #8374 * #8375 These patches and spkg's are applied on top of Sage 4.3.3. The build is still going on these machines: * sage.math * bsd.

Re: [sage-devel] How can I best debug doctest failures ??

William Stein wrote: On Mon, Mar 1, 2010 at 4:41 AM, Dr. David Kirkby wrote: There are 5 doctests which are failing on Solaris. 4 seem to related, the 5th not. Can anyone suggest anything that might cause the first 4 to fail? sage -t "devel/sage/sage/graphs/graph_list.py" # Segfault sage -t

[sage-devel] Re: GSOC

On Mar 1, 1:48 pm, "Dr. David Kirkby" wrote: > Perhaps one should consider what fits in best with the Google business model. > They organize information and make it universally useful. Sage doesn't help and what you suggest only overlaps with their own search engine efforts. Their vision is a sea

[sage-devel] Update upstream version. Patch levels starts at p0 ???

I've just been looking at the SPKG.txt for sqlite and see: === sqlite-3.6.19.p0 (Mike Hansen, October 26th, 2009) === * Updated to 3.6.19 with http://sqlite.org/sqlite-amalgamation-3.6.19.tar.gz. === sqlite-3.6.17.p0 (Dan Drake, October 25th, 2009) === * Remove obsolete Makefile.in "patch" fo

[sage-devel] Re: Sage Days 20 Status Report

On Mar 1, 12:14 pm, Sébastien Labbé wrote: >  A french >   discussion list perhaps with an associated web site (sage-edu.fr or >   sagemath-edu.fr) will be open soon. You report sounds incredibly good for Sage. And about the website: once there are more french websites online, can you tell me or

Re: [sage-devel] Re: GSOC

William Stein wrote: Yes, I think there should be a Sage GSOC application. I'm OK with being listed as a mentor. However, I won't write the actual application, since I wrote three applications in a row that were all turned down, so clearly I don't know how to write one. What happened last ye

Re: [sage-devel] How can I best debug doctest failures ??

On Mon, Mar 1, 2010 at 4:41 AM, Dr. David Kirkby wrote: > There are 5 doctests which are failing on Solaris. 4 seem to related, the > 5th not. Can anyone suggest anything that might cause the first 4 to fail? > > sage -t  "devel/sage/sage/graphs/graph_list.py" # Segfault > sage -t  "devel/sage/sag

[sage-devel] How can I best debug doctest failures ??

There are 5 doctests which are failing on Solaris. 4 seem to related, the 5th not. Can anyone suggest anything that might cause the first 4 to fail? sage -t "devel/sage/sage/graphs/graph_list.py" # Segfault sage -t "devel/sage/sage/graphs/generic_graph.py" # Segfault sage -t "devel/sage/sage/

Re: [sage-devel] Is CMake OK for a standard spkg?

On Sun, Feb 28, 2010 at 11:40 PM, Peter Jeremy wrote: >>For what is worth, we use cmake in FEMhub (femhub.org) as a standard >>package and we never had any problems with that. > > If CMake was widely used (and hence can be listed as a prerequisite for > building Sage - like gmake, bash etc) then

[sage-devel] Re: gsoc ideas list

On 02/28/2010 02:02 PM, Burcin Erocal wrote: Hi, After the recent thread about Google Summer of Code [1], I set up a wiki page to collect project ideas: http://wiki.sagemath.org/gsoc10 [1] http://groups.google.com/group/sage-devel/t/8f61382c855ddb09 The application window for mentoring organ

Re: [sage-devel] Is CMake OK for a standard spkg?

Peter Jeremy wrote: On 2010-Feb-28 21:32:10 -0800, Ondrej Certik wrote: I like cmake and I use it for all my projects, that involve some C++ coding. There are lots of make-like tools available and different people use different ones. One disadvantage of this is that where a large project p

[sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".

Hi, I've created this trac wiki page with a subset of the 10 most important current bug/issues in Sage, according to votes in this thread: http://trac.sagemath.org/sage_trac/wiki/stab1 These are all bugs/issues that many people care about. None are highly specialized. So if anybody

Re: [sage-devel] Any Solaris user want to review a really ugly patch ??

Dr. David Kirkby wrote: That ticket is a *huge* improvement in that 1) 'prstat' exits as part of the operating system. Oops, a typo that could be confusing. 'prstat' *exists* as part of the Solaris 10 operating system, whereas 'top' does not. Dave -- To post to this group, send an email t

Re: [sage-devel] Any Solaris user want to review a really ugly patch ??

Peter Jeremy wrote: On 2010-Feb-28 01:48:35 +, "Dr. David Kirkby" wrote: and dirty ugly patch, I've changed the call to 'top' from one to 'prstat' on Solaris. Unlike 'top', 'prstat' is standard command. I call it 'ugly' as I don't think calling 'prstat' it an ideal way, but it is better

[sage-devel] Sage Days 20 Status Report

Sage Days 20 are now over: http://www.lirmm.fr/arith/wiki/MathInfo2010/SageDays Below is a text written by Nicolas Thiéry, Vincent Delecroix, Sébastien Labbé and Julien Cassaigne about the week. Participants are welcome to complete it if necessary. *** This was a pretty intense week with ab

[sage-devel] Re: Is CMake OK for a standard spkg?

Bjarke Hammersholt Roune wrote: If Singular moves to CMake that could seriously be a pain for us, since we'll likely have to add cmake as a standard package to Sage, which will of course involves headaches. OK - thanks for the information. There would be advantages to CMake, too, e.g. it works

[sage-devel] Re: Is CMake OK for a standard spkg?

> If Singular moves to CMake that could seriously be a pain for us, > since we'll likely have to add cmake as a standard package to Sage, > which will of course involves headaches. > OK - thanks for the information. There would be advantages to CMake, too, e.g. it works on lots of platforms like So

Re: [sage-devel] Return type for coefficient

On 1 March 2010 03:51, Kwankyu Lee wrote: > Hi, > > I want to raise this issue again. > > sage: P. = PolynomialRing(QQ,2) > sage: f = 2*x*y+x+y > sage: f.coefficient({x:1,y:1}) > 2 > sage: c = f.coefficient({x:1,y:1}) > sage: c.parent() > Multivariate Polynomial Ring in x, y over Rational Field >

Re: [sage-devel] Mutability and Cython...

Hello, On Mon, Mar 1, 2010 at 1:10 AM, Florent Hivert wrote: > I'm doing some cleanup in mutability, but I'm rather new to Cython. I there > any reason (aside backward compatibility) to have these two following methods > rather than a cpdef ? Nope, I believe that these were written before cpdef

[sage-devel] Mutability and Cython...

Hi there, I'm doing some cleanup in mutability, but I'm rather new to Cython. I there any reason (aside backward compatibility) to have these two following methods rather than a cpdef ? def _require_mutable(self): if self._is_immutable: raise ValueError, "object is i

Re: [sage-devel] 0 < sqrt3 is False in QuadraticField

Hi Sebastien, > I am currently experiencing some problems when comparing elements of a > QuadraticField. See below. I'm not sure this is exactly the same but I think Nicolas (the little) is working on this: Ticket #8347 Test the positivity of a number field element Florent -- To post to

Re: [sage-devel] Sanity check on objects, parents and elements

Hi Robert, >> You get the point. As far as I understand a RIF only return True if the >> interval are reduced to a single point. Is it right ? It would be better >> to >> return a special value like Unknown than False. But that's another >> question... >> >> [...] > > I certainly agree tha

Re: [sage-devel] Sanity check on objects, parents and elements

> I certainly agree that 1-2 should be the general rule, I was just pointing > out an exception. I like the idea of returning an Unknown object on RIF > comparisons as well. This is now #8402 (work in progress). Florent -- To post to this group, send an email to sage-devel@googlegroups.com To

[sage-devel] Re: make test fails on over 100 items with sage-4.3.3

In the spirit of not wasting computational resources, I have decided to go with David Roe's idea: Don't worry about it too much Greetings, Erwin On Feb 26, 8:15 pm, mhampton wrote: > You could try stressing that install a little more by testing with the > "-long" option.  If those pass then I w