[sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

2012-03-04 Thread Keshav Kini
François Bissey writes: > On Sun, 04 Mar 2012 00:02:57 Michael Orlitzky wrote: >> On 03/03/2012 07:50 PM, François Bissey wrote: >> > No, I was refering to the ability to clone the sage hg repository and >> > switch to your own "homebrew" version of sage by running "sage -b". That >> > isn't suppo

Re: [sage-devel] Re: trac field names -- arrrrr!

2012-03-04 Thread Robert Bradshaw
On Sat, Mar 3, 2012 at 12:15 PM, Michael Orlitzky wrote: > On 03/02/2012 02:29 PM, kcrisman wrote: >> >> >> IF the patchbot actually applied the right patches to the right >> development version, naturally, which I suppose is what you mean in >> the next line? >> > > I meant that it would suck if

Re: [sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

2012-03-04 Thread Robert Bradshaw
On Sun, Mar 4, 2012 at 12:10 AM, Keshav Kini wrote: > François Bissey writes: >> On Sun, 04 Mar 2012 00:02:57 Michael Orlitzky wrote: >>> On 03/03/2012 07:50 PM, François Bissey wrote: >>> > No, I was refering to the ability to clone the sage hg repository and >>> > switch to your own "homebrew"

Re: [sage-devel] Sage security

2012-03-04 Thread Robert Bradshaw
On Sat, Mar 3, 2012 at 7:59 AM, Jeroen Demeyer wrote: > On 2012-03-02 18:31, Jan Groenewald wrote: >> Are all notebook users running as the same sage user? > Yes. > >> How could sage users be separated? > We could map Sage notebook users to Unix separate Unix users, but then > the Sage notebook se

[sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

2012-03-04 Thread Keshav Kini
William Stein writes: > Moreover, "upstream" includes a huge number of versions of Linux > distributions, > versions of OS X, Solaris, etc.  It is only by caring about actual users (who > usually don't have root) that one can begin to comprehend the problem a > monolithic distribution of Sage sol

Re: [sage-devel] Re: sage cell server and doctests

2012-03-04 Thread Robert Bradshaw
On Sat, Mar 3, 2012 at 11:00 AM, Jason Grout wrote: > On 3/3/12 12:57 PM, kcrisman wrote: >> >> >> >> On Mar 3, 10:44 am, Jason Grout  wrote: >>> >>> Here's a crazy idea: >>> >>> What if we included a bit of javascript in with the Sage html >>> documentation that added a little "Try it!" button to

Re: [sage-devel] Re: Group collaboration on a branch of Sage

2012-03-04 Thread Robert Bradshaw
On Fri, Mar 2, 2012 at 11:31 PM, Julien Puydt wrote: > Le samedi 03 mars, Ivan Andrus a écrit: >> I assume (since it's git) that there is some magic that will let me >> specify N branches and then merge them into an unnamed branch that I >> can then use to build and run the version I'm interested

Re: [sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

2012-03-04 Thread Julien Puydt
Le dimanche 04 mars, Keshav Kini a écrit: > William Stein writes: > > Moreover, "upstream" includes a huge number of versions of Linux > > distributions, versions of OS X, Solaris, etc.  It is only by > > caring about actual users (who usually don't have root) that one > > can begin to comprehend

Re: [sage-devel] Re: Unifying Command line options

2012-03-04 Thread R. Andrew Ohana
On Mar 3, 2012 11:47 PM, "Jeroen Demeyer" wrote: > > On 2012-03-04 00:21, R. Andrew Ohana wrote: > > Also, I would like to decouple the sage-scripts spkg from sage > > releases, since in many cases it seems like the only change is a > > version bump. I've added SAGE_VERSION and SAGE_RELEASE_DATE t

[sage-devel] Re: Unifying Command line options

2012-03-04 Thread Keshav Kini
"R. Andrew Ohana" writes: > I've created a repo on github: github.com/ohanar/sagescripts >From https://github.com/ohanar/sagescripts/blob/master/README : > it should be relatively easy at this point to move old bash scripts > into this repo (python scripts to come) Wait, are you planning to just

Re: [sage-devel] Re: Group collaboration on a branch of Sage

2012-03-04 Thread Robert Bradshaw
On Fri, Mar 2, 2012 at 5:35 AM, Keshav Kini wrote: > Robert Bradshaw writes: >> On Fri, Mar 2, 2012 at 1:45 AM, Keshav Kini wrote: >>> For example, if two >>> people have branches named trac-n, the script should just do nothing, >>> not try to pick the most recently updated one, or look for bran

Re: [sage-devel] Re: Unifying Command line options

2012-03-04 Thread Robert Bradshaw
On Sat, Mar 3, 2012 at 3:21 PM, R. Andrew Ohana wrote: > I've created a repo on github: github.com/ohanar/sagescripts > > Much of the backbone has been setup, although I've ported very few > actual scripts (the ones there are mainly to test that my generating > code actually does what I want it to

[sage-devel] Re: Group collaboration on a branch of Sage

2012-03-04 Thread Keshav Kini
Martin Albrecht writes: > On Friday 02 Mar 2012, Keshav Kini wrote: >> The main thing that github "does better" is probably to have a userbase >> about ten times the size of bitbucket, which means it's much more likely >> to find your current collaborators already on github than to find them >> al

Re: [sage-devel] Re: Unifying Command line options

2012-03-04 Thread R. Andrew Ohana
On Mar 4, 2012 3:12 AM, "Robert Bradshaw" wrote: > > On Sat, Mar 3, 2012 at 3:21 PM, R. Andrew Ohana wrote: > > I've created a repo on github: github.com/ohanar/sagescripts > > > > Much of the backbone has been setup, although I've ported very few > > actual scripts (the ones there are mainly to

Re:[sage-devel] Re: Unifying Command line options

2012-03-04 Thread R. Andrew Ohana
On Mar 4, 2012 2:42 AM, "Keshav Kini" wrote: > > "R. Andrew Ohana" writes: > > I've created a repo on github: github.com/ohanar/sagescripts > > From https://github.com/ohanar/sagescripts/blob/master/README : > > it should be relatively easy at this point to move old bash scripts > > into this rep

[sage-devel] Re: Group collaboration on a branch of Sage

2012-03-04 Thread Keshav Kini
Robert Bradshaw writes: > On Fri, Mar 2, 2012 at 5:35 AM, Keshav Kini wrote: >> I would actually like the patchbot to NOT do continuous builds and >> tests, once we move to a push/pull system. There should be a big button >> on each ticket which says "Test Me!", which will cause the patchbot to >

[sage-devel] Re: Unifying Command line options

2012-03-04 Thread Keshav Kini
"R. Andrew Ohana" writes: > I mainly wanted a clean repo to start with, but given how simple it is to move > over scripts now, I'll see about basing it off of the current scripts repo > next > time I work on it. I converted the current scripts repo to git and put it on the sagemath org on github

[sage-devel] Re: Natural language interface to sage

2012-03-04 Thread Keshav Kini
Michael Orlitzky writes: > On 03/01/12 23:43, Keshav Kini wrote: >> I don't understand. Why would it be *faster* to do version bumps if >> sage-on-gentoo gets into Gentoo proper? Overlays are always more nimble >> than the Gentoo tree, as far as I can see. > > If we're to distribute sage via sourc

[sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

2012-03-04 Thread Keshav Kini
Julien Puydt writes: > What monolithic certainly means is that it's harder to package, harder > to port and bigger to install. > > In some way, sage isn't that modular : here and there, things are > hardcoded which makes the modules not-really-independent, and in an > implicit way, so you only kno

[sage-devel] Re: Natural language interface to sage

2012-03-04 Thread rjf
On Saturday, March 3, 2012 11:02:39 AM UTC-8, kcrisman wrote: ... > > Has anyone ever done a natural-language frontend attempt to Maxima or > its predecessors? I would be surprised if someone hadn't, to be > honest. > > I am unaware of any natural language front end to Macsyma or Maxima,

Re: [sage-devel] Re: Unifying Command line options

2012-03-04 Thread Jeroen Demeyer
On 2012-03-04 11:29, R. Andrew Ohana wrote: > Can you be more specific? Introducing the two variables or decoupling > sage-scripts? I meant "decoupling sage-scripts". And the consequences all depend on the approach you're taking. Anyway, there already is a ticket but no consensus on how to do it:

Re: [sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

2012-03-04 Thread Michael Orlitzky
On 03/04/2012 01:15 AM, François Bissey wrote: That's a bit more complicated than that. But in essence yes you can. Now do you know how to get your version of the library to be used instead of the system one? Getting a copy and recompiling it is just hum. 2/3 of the story (just so you kn

[sage-devel] Fwd: Problem building Sage from source

2012-03-04 Thread Amy Feaver
Hi Sage Developers, I'm trying to install Sage on multiple computers in a network to run my code simultaneously on all of them. At CU, all of the department computers share a filesystem but might have different versions of RedHat Linux or different dependencies installed. I just tried to install

[sage-devel] Making simplification safe

2012-03-04 Thread Michael Orlitzky
Right now, we have a problem with simplification. There are a couple of open tickets about it, and an Ask Sage thread, but it's easier to give an example (thanks to logix on IRC for the minimal test case): sage: f = sqrt(x^2 + 2*x + 1) sage: f.full_simplify() x + 1 I think the user shoul

[sage-devel] Re: Problem building Sage from source

2012-03-04 Thread Volker Braun
The most obvious problem is the "Clock skew detected" messages. This means that your desktop clock is not synchronized with the network file server. You basically can't compile stuff unless clocks agree on server and client. While you are at it, you can ask your admin to install the atlas and a

Re: [sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

2012-03-04 Thread François Bissey
On Sun, 04 Mar 2012 17:51:47 Michael Orlitzky wrote: > On 03/04/2012 01:15 AM, François Bissey wrote: > > That's a bit more complicated than that. But in essence yes you can. > > Now do you know how to get your version of the library to be used > > instead of the system one? Getting a copy and reco

[sage-devel] Re: Problem building Sage from source

2012-03-04 Thread Amy Feaver
Hi Volker, Thanks for your help. Unfortunately, I don't quite understand what you're suggesting that I do. It sounds like I can't remotely 'make' sage because when I do, the cpu clocks are getting out of sync (what does it mean that the host is throttled and why would it be?). I think that the f

[sage-devel] Re: the state of dense linear algebra in Sage

2012-03-04 Thread Dima Pasechnik
In gmane.comp.mathematics.sage.devel, you wrote: > On Mar 2, 2:59 am, Martin Albrecht > wrote: >> which collects this information. I am not done yet filling it in, but I have >> to catch a train now. Meaning: knock yourselves out adding/filling in your >> favourite base ring :) > > Not my favorite

[sage-devel] Support for the @property decorator?

2012-03-04 Thread Maarten Derickx
This is standard python behaviour. I suggest that you just make the documentation of the first function explain how to both get and set the domain. -- 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...@goo

[sage-devel] Re: Sage 4.8 build failed: Error: Failed to build Maxima as an ECL library.

2012-03-04 Thread syd.lavas...@gmail.com
Hello Dmitrii, Thank you very much for looking to my case. I have uploaded it here, good luck with this 90Mb file: http://payamban.com/install.log Moreover, maybe this information is also useful: ~/sage $ cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.8 (Tikanga) ~/sage $ gc

[sage-devel] Re: Problem building Sage from source

2012-03-04 Thread Volker Braun
You should send a polite email to your system admin requesting that a) the computer you are using and/or the file server have their clocks synchronized (this is a really basic issue and must be fixed independently of Sage) b) atlas and atlas-devel be installed on all computers that you plan on