[sage-devel] Automatic or manual parallel stuff

2011-11-11 Thread Jeroen Demeyer
Right now, there are several parts of the Sage scripts having support for doing things in parallel: - Building Sage itself with SAGE_PARALLEL_SPKG_BUILD (which is now the default) - Source files in the same spkg - Sage library (sage -b) - Doctesting (sage -tp, make ptestlong) - With #6495, building

Re: [sage-devel] Debian Version?

2011-11-11 Thread Francois Bissey
> On Fri, Nov 11, 2011 at 12:59 PM, frosty wrote: > > I have just discovered Sage & want to know if there are any folks here > > working on making a Debian version that would work without having to > > compile all the parts. i.e. use the needed files, apps & libraries > > that are already packaged

Re: [sage-devel] Debian Version?

2011-11-11 Thread Jeroen Demeyer
On 2011-11-11 21:59, frosty wrote: > Secondly I have downloaded the binary for Linux and have it installed > & runnimng: I want to actually compile Sage for my server which is an > AMD 6 core based server with 8Gb of ram running Debian stable. I > tried , but it errored out, error 1 showing a segme

Re: [sage-devel] Debian Version?

2011-11-11 Thread William Stein
On Fri, Nov 11, 2011 at 12:59 PM, frosty wrote: > I have just discovered Sage & want to know if there are any folks here > working on making a Debian version that would work without having to > compile all the parts. i.e. use the needed files, apps & libraries > that are already packaged in Debian

[sage-devel] Re: Removing "doc" dependency from test targets

2011-11-11 Thread John H Palmieri
On Friday, November 11, 2011 2:45:08 PM UTC-8, Jeroen Demeyer wrote: > > I am considering removing the "doc" dependency from the test targets > (like ptestlong). I am regularly annoyed by the long time it takes to > rebuild the docs > > > How about reviewing #6495 instead? It cuts down the time

Re: [sage-devel] Removing "doc" dependency from test targets

2011-11-11 Thread William Stein
On Fri, Nov 11, 2011 at 2:45 PM, Jeroen Demeyer wrote: > I am considering removing the "doc" dependency from the test targets > (like ptestlong).  I am regularly annoyed by the long time it takes to > rebuild the docs when doing "make ptestlong".  It is true that a few > doctests would fail if no

[sage-devel] Removing "doc" dependency from test targets

2011-11-11 Thread Jeroen Demeyer
I am considering removing the "doc" dependency from the test targets (like ptestlong). I am regularly annoyed by the long time it takes to rebuild the docs when doing "make ptestlong". It is true that a few doctests would fail if no documentation has been built. But if the documentation has been

Re: [sage-devel] Debian Version?

2011-11-11 Thread David Roe
Welcome to Sage! There was an effort a couple years ago to get Sage as a debian package. It was successful for a while, but then the maintainer left academia and founded a startup, so it hasn't been upgraded. I think one of the problems is getting a fairly current version of Sage into Debian. I

[sage-devel] Contracting edges in bipartite graphs

2011-11-11 Thread Stefan van Zwam
Dear all, I encountered some undesirable behavior when trying to contract an edge in a bipartite graph: sage: G = graphs.CompleteBipartiteGraph(3,3) sage: G.merge_vertices([1,4]) Yields: RuntimeError: Edge vertices must lie in different partitions. sage: G.num_verts() 5 I'm ok with not being

[sage-devel] Debian Version?

2011-11-11 Thread frosty
I have just discovered Sage & want to know if there are any folks here working on making a Debian version that would work without having to compile all the parts. i.e. use the needed files, apps & libraries that are already packaged in Debian. Secondly I have downloaded the binary for Linux and hav

[sage-devel] Encoding of .py files

2011-11-11 Thread Jeroen Demeyer
Is there a requirement that all Sage .py files should be ASCII or is UTF8 also accepted? It seems that Sphinx 1.1.2 (#10620) cares more about this: at #10112 there is a patch with a 0xd0 byte (which is neither ASCII neither UTF8) which is rejected by Sphinx 1.1.2. Jeroen. -- To post to this gro

Re: [sage-devel] Re: or sage-5.0? (Re: [sage-release] Next release: sage-4.7.3 or sage-4.8?)

2011-11-11 Thread Julien Puydt
Le 08/11/2011 17:04, Michael Orlitzky a écrit : In any case, the "do them both" approach is fine until one is so obviously superior that the other side can be convinced. Just to make my position clear again ; I'm for the "do them both" approach. And I don't call for breaking anything at once,

[sage-devel] Re: feature request: store additional information about symbolic variables

2011-11-11 Thread Stan Schymanski
For the record, I found a way that works for me quite well now: udict = {} cdict = {} docdict = {} def var2(name,doc='',units='',domain1='real',latexname='',value = -1234): ''' Creates a symbolic variable in the given domain (standard:'real') and with the given latexname. Further, it

[sage-devel] Re: or sage-5.0? (Re: [sage-release] Next release: sage-4.7.3 or sage-4.8?)

2011-11-11 Thread ancienthart
Have to put my vote in for the virtual image. Except for R graphics (which I have issues with on Linux :P), it does everything I want to do. Volker Braun does awesome work. Joal Heagney -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send

[sage-devel] Re: or sage-5.0? (Re: [sage-release] Next release: sage-4.7.3 or sage-4.8?)

2011-11-11 Thread Georg S. Weber
On 10 Nov., 13:33, Maarten Derickx wrote: > I like your ideas about guest distributions Georg. > Thanks! > The missing thing you describe: "a way to tell the host distrubution on > what packages we depend" is not really the missing thing. I think a way to > make sage configurable to use other