Re: [sage-devel] Re: sage android project

Le dimanche 18 mars, Akshay a écrit: > I'm curious, are there Lisp implementations that run on ARM, upon > which Maxima can be compiled ? I guess ECL will work (not sure > though). Sage is ported on ubuntu/ARM already ; and ecl mostly works, apart for a single failing doctest : http://sourceforge.

Re: [sage-devel] Re: Upgrading trac

The download image next to the files/patches attached to a ticket is no longer showing. Looking at the source, it seems that it is missing this img line: On Monday, March 19, 2012 10:20:02 AM UTC+8, R. Andrew Ohana wrote: > > Trac is more or less working, please report any bugs. > -- To pos

Re: [sage-devel] Re: sage android project

I'm curious, are there Lisp implementations that run on ARM, upon which Maxima can be compiled ? I guess ECL will work (not sure though). -- 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...@googlegroups.

[sage-devel] Re: Upgrading trac

On Mar 18, 9:31 pm, David Roe wrote: > Known issues: Known improvements: * Comments can be edited. * Seems super-fast compared to before. * No need to scroll bottom to top to bottom to preview changes to the description, there are link-buttons to jump back/forth. ("Modify" + "View") Thank

Re: [sage-devel] Re: Upgrading trac

On Sun, Mar 18, 2012 at 21:10, leif wrote: > On 19 Mrz., 03:20, "R. Andrew Ohana" wrote: > > Trac is more or less working, please report any bugs. > > More or less? :-) > Known issues: * The link to the patchbot has disappeared (thanks for pointing that out Dima). We understand what happened

Re: [sage-devel] Re: Upgrading trac

On Mar 18, 2012, at 19:20 , R. Andrew Ohana wrote: > Trac is more or less working, please report any bugs. A couple of minor glitches: - I refreshed a previously-open page displaying #12555. Before the refresh, I was shown as logged in. After the refresh, I was not. A second refresh got me

Re: [sage-devel] Re: Upgrading trac

On Monday, 19 March 2012 10:20:02 UTC+8, R. Andrew Ohana wrote: > > Trac is more or less working, please report any bugs. where is the patchbot icon on the tickets? It has vanished. > > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group,

[sage-devel] Re: Upgrading trac

On 19 Mrz., 05:10, leif wrote: > On 19 Mrz., 03:20, "R. Andrew Ohana" wrote: > Do the trac pages have to be centered? > > To me it's a bit inconvenient, and it *may* give problems if the > (preview) pages get extremely wide due to some plugin weirdness, not > wrapping overlong lines. > > I'll try

[sage-devel] Re: Upgrading trac

On 19 Mrz., 03:20, "R. Andrew Ohana" wrote: > Trac is more or less working, please report any bugs. More or less? :-) Do the trac pages have to be centered? To me it's a bit inconvenient, and it *may* give problems if the (preview) pages get extremely wide due to some plugin weirdness, not wrap

Re: [sage-devel] Re: Upgrading trac

Trac is more or less working, please report any bugs. On Sun, Mar 18, 2012 at 18:47, David Roe wrote: > Trac will go down in 5 minutes. > David > > > On Sun, Mar 18, 2012 at 21:10, Keshav Kini wrote: >> >> David Roe writes: >> > Strange.  We haven't actually done anything yet related to the upg

Re: [sage-devel] Re: new list?

On Sun, 18 Mar 2012 at 06:44PM -0700, Keshav Kini wrote: > Dan Drake writes: > > I'm afraid that, by pushing GSoC students to a different list, we would > > be in effect creating two classes of developers. It would be a bit like > > having the "grownups table" and "kids table" at holiday meals. >

Re: [sage-devel] Re: sage android project

On Sun, 18 Mar 2012 at 09:34PM +0530, Jeh Agarwal wrote: > but still its a long way till it becomes common...how many would have > such powerful devices now??? Right now: very few. But what about a year from now? Two years? Two years ago at my university, smartphones were something that only rich

Re: [sage-devel] Re: Upgrading trac

Trac will go down in 5 minutes. David On Sun, Mar 18, 2012 at 21:10, Keshav Kini wrote: > David Roe writes: > > Strange. We haven't actually done anything yet related to the upgrade, > so I > > don't know what to tell you. > > David > > > > On Sun, Mar 18, 2012 at 20:34, Hugh Thomas > wrote:

[sage-devel] Re: new list?

Dan Drake writes: > I'm afraid that, by pushing GSoC students to a different list, we would > be in effect creating two classes of developers. It would be a bit like > having the "grownups table" and "kids table" at holiday meals. I don't think the point is to move GSoC students to a different li

Re: [sage-devel] new list?

On Sat, 17 Mar 2012 at 05:58PM +, John Cremona wrote: > Would anyone else like to see all this google stuff moved to a > different mailing list? On Sat, 17 Mar 2012 at 11:07AM -0700, William Stein wrote: > YES! I guess it's too late now, but I would prefer to keep everything on sage-devel. We

[sage-devel] Re: Upgrading trac

David Roe writes: > Strange.  We haven't actually done anything yet related to the upgrade, so I > don't know what to tell you. > David > > On Sun, Mar 18, 2012 at 20:34, Hugh Thomas wrote: > > > Twice, today, instead of the page I was expecting, trac produced something > like this: > >

Re: [sage-devel] Re: Upgrading trac

Strange. We haven't actually done anything yet related to the upgrade, so I don't know what to tell you. David On Sun, Mar 18, 2012 at 20:34, Hugh Thomas wrote: > > Twice, today, instead of the page I was expecting, trac produced something > like this: > > Traceback (most recent call last): >

[sage-devel] Re: Upgrading trac

Twice, today, instead of the page I was expecting, trac produced something like this: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/Trac-0.11.5-py2.5.egg/trac/web/api.py", line 377, in send_error 'text/html') File "/usr/lib/python2.5/site-packages/Trac-0.11

[sage-devel] GSoC applicants - sage-gsoc or sage-devel?

Hi Harald, http://www.google-melange.com/gsoc/org/google/gsoc2012/sage talks about sage-gsoc, but the "Ideas" document talks about sage-devel for essentially the same purpose. Should you fix the latter to point t

Re: [sage-devel] Physical constants

What you are doing using the units package is almost exactly what I do except that I only have definitions for the units I encounter commonly. I'd have to add acres and roods in terms of m to the list I maintain to do the equivalent of your example. The difference is that when I write an expr

Re: [sage-devel] Evil segfault bug in matrix solve_left

On Sun, Mar 18, 2012 at 2:15 PM, William Stein wrote: > On Sun, Mar 18, 2012 at 12:19 PM, David Loeffler > wrote: >> Hi folks, >> >> I just hit a rather evil linear algebra bug, which results in an instant >> segfault: >> >> sage: A = identity_matrix(ZZ, 2, sparse=True) >> sage: B = identity_matr

Re: [sage-devel] Evil segfault bug in matrix solve_left

On Sun, Mar 18, 2012 at 12:19 PM, David Loeffler wrote: > Hi folks, > > I just hit a rather evil linear algebra bug, which results in an instant > segfault: > > sage: A = identity_matrix(ZZ, 2, sparse=True) > sage: B = identity_matrix(ZZ, 2, sparse=True) > sage: A.solve_left(B) > /storage/masiao/s

Re: [sage-devel] Math typesetting for inputs in the notebook

> > That ticket pretty much covers what I want to implement; do you think that > is suitable for a GSoC project? > > -- 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...@googlegroups.com For more options,

[sage-devel] Re: Math typesetting for inputs in the notebook

That's a correct reading, I'll be primarily be targeting the 2nd point about improving the readability of large expressions, and I believe math typesetting will also make such inputs easier. Your first point about color coding arguments is also something that I could work on. On Sunday, March 1

Re: [sage-devel] Physical constants

On Sun, Mar 18, 2012 at 11:33 AM, Jonathan wrote: > I  simply define my fundamental unit system and define all units relative to > that.  Typically I use SI units kg, m and s. Then I define other convenient > quantities. For example "cm=m*1e-2" Then when I enter "10.0 cm" in an > expression sag

[sage-devel] Evil segfault bug in matrix solve_left

Hi folks, I just hit a rather evil linear algebra bug, which results in an instant segfault: sage: A = identity_matrix(ZZ, 2, sparse=True) sage: B = identity_matrix(ZZ, 2, sparse=True) sage: A.solve_left(B) /storage/masiao/sage-5.0.beta8/spkg/bin/sage: line 308: 7843 Segmentation fault sage-

Re: [sage-devel] Physical constants

Oops! I see a typo...I meant input "10.0*cm" -- 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http:/

Re: [sage-devel] Physical constants

I simply define my fundamental unit system and define all units relative to that. Typically I use SI units kg, m and s. Then I define other convenient quantities. For example "cm=m*1e-2" Then when I enter "10.0 cm" in an expression sage interprets it as 0.100*m. If I want the answer in particu

[sage-devel] Upgrading trac

Hi everyone, We're looking at upgrading trac from 0.11.5 to 0.12.3 (latest stable version). There will probably be some downtime later today (hopefully less than 10 minutes) to switch over to the new version. Let us know if today is a bad day for some reason, and also if something is misbehaving

Re: [sage-devel] Re: sage android project

Le dimanche 18 mars, Jeh Agarwal a écrit: > but still its a long way till it becomes common...how many would have > such powerful devices now??? Good code just ports itself. Especially if it's possible to do it by morsels. It's possible to make sage more flexible already, so it handles the future

Re: [sage-devel] Re: Basing new development versions of Sage on the previous development version

Le dimanche 18 mars, William Stein a écrit: > Does git magically solve that problem? No, but it mitigates it. It's a tool. It won't prevent you from hitting on your fingers if you insist on it, but it will make your life easier in general. Snark on #sagemath -- To post to this group, send an em

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

On Thursday, March 15, 2012 5:25:13 PM UTC+1, Nils Bruin wrote: > > On Mar 15, 12:21 am, "syd.lavas...@gmail.com" > wrote: > > The problem is that my home directory is: > > > > /files3/home/sahosse/ > > > > but I only have execution permission to the directory "home": > > I confirm: > > $

[sage-devel] Applied Math

Greetings to the team I am Nitish Kr. Jaipuria, a 4th year student of the Department of Mathematics, IIT Kharagpur, enrolled in 5 year Integrated MS course of mathematics and computing. Due to my course content I have adequate knowledge of both maths and computer science. I am very much interested

[sage-devel] Re: sage android project

Jeh Agarwal writes: > but still its a long way till it becomes common...how many would have such > powerful devices now??? Right, I don't think anyone is disagreeing with you. The main priority is to make remote operation of Sage possible (and easy, and nice looking, and useful) on mobile devices

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

On Friday, March 16, 2012 1:04:35 AM UTC+1, leif wrote: > > Btw, you run into similar problems if you happen to have HOME set but > the directory doesn't exist (e.g. because /home isn't mounted); ECL > insists on being at least able to *read* your home directory. > Is it so surprising given tha

Re: [sage-devel] Re: sage android project

but still its a long way till it becomes common...how many would have such powerful devices now??? On Sun, Mar 18, 2012 at 12:00 PM, Dima Pasechnik wrote: > > > On Sunday, 18 March 2012 00:48:48 UTC+8, Harald Schilly wrote: >> >> >> >> On Saturday, March 17, 2012 5:14:17 PM UTC+1, Jeh Agarwal wr

[sage-devel] Re: Basing new development versions of Sage on the previous development version

William Stein writes: > On Sun, Mar 18, 2012 at 8:31 AM, Keshav Kini wrote: >> William Stein writes: >>> On Sun, Mar 18, 2012 at 7:59 AM, Keshav Kini wrote: William Stein writes: > On Sun, Mar 18, 2012 at 5:45 AM, Jeroen Demeyer > wrote: >> On 2012-03-17 14:39, Keshav Kini w

Re: [sage-devel] Re: Basing new development versions of Sage on the previous development version

On Sun, Mar 18, 2012 at 8:31 AM, Keshav Kini wrote: > William Stein writes: >> On Sun, Mar 18, 2012 at 7:59 AM, Keshav Kini wrote: >>> William Stein writes: On Sun, Mar 18, 2012 at 5:45 AM, Jeroen Demeyer wrote: > On 2012-03-17 14:39, Keshav Kini wrote: >> If you instead tel

[sage-devel] Re: Basing new development versions of Sage on the previous development version

William Stein writes: > On Sun, Mar 18, 2012 at 7:59 AM, Keshav Kini wrote: >> William Stein writes: >>> On Sun, Mar 18, 2012 at 5:45 AM, Jeroen Demeyer >>> wrote: On 2012-03-17 14:39, Keshav Kini wrote: > If you instead tell people to base > their patches on the stable release >>

[sage-devel] Re: Physical constants

By the way, this ticket might be of interest: http://trac.sagemath.org/sage_trac/ticket/9763 -Keshav Join us in #sagemath on irc.freenode.net ! -- 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...@g

Re: [sage-devel] Re: Basing new development versions of Sage on the previous development version

On Sun, Mar 18, 2012 at 7:59 AM, Keshav Kini wrote: > William Stein writes: >> On Sun, Mar 18, 2012 at 5:45 AM, Jeroen Demeyer >> wrote: >>> On 2012-03-17 14:39, Keshav Kini wrote: If you instead tell people to base their patches on the stable release >>> I certainly don't want this.

Re: [sage-devel] Physical constants

On Sun, Mar 18, 2012 at 8:07 AM, Jonathan wrote: > A few things: > 1) This definitely should be separable from units.  And although we have a > units package, I still find it easier to simply use variables as units. Just out of curiosity, how do you do conversions? That's the main thing I use t

Re: [sage-devel] Physical constants

I found the documentation of the "uncertainties" package. It is not as powerful as using the general expression I provided above inside Sage because there is only a limited set of analytical derivatives the package knows about and then it uses a robust digital differentiation scheme for other

Re: [sage-devel] Physical constants

A few things: 1) This definitely should be separable from units. And although we have a units package, I still find it easier to simply use variables as units. 2) Scientific data typically is available as numbers 3.56 +/- 0.02 where the 0.02 is either the standard deviation or more often the 95%

[sage-devel] Re: Basing new development versions of Sage on the previous development version

William Stein writes: > On Sun, Mar 18, 2012 at 5:45 AM, Jeroen Demeyer > wrote: >> On 2012-03-17 14:39, Keshav Kini wrote: >>> If you instead tell people to base >>> their patches on the stable release >> I certainly don't want this. >> >>> Why do patches need to be based on the latest dev rele

Re: [sage-devel] Re: Basing new development versions of Sage on the previous development version

On Sunday, 18 March 2012 20:57:54 UTC+8, William wrote: > > On Sun, Mar 18, 2012 at 5:45 AM, Jeroen Demeyer <> wrote: > > On 2012-03-17 14:39, Keshav Kini wrote: > >> If you instead tell people to base > >> their patches on the stable release > > I certainly don't want this. > > > >> Why do patch

Re: [sage-devel] Math typesetting for inputs in the notebook

On Sat, Mar 17, 2012 at 11:46 PM, Yukun wrote: > Hi all, > > I'm a 1st year CS student interested in doing a GSoC project this summer. I > played around with the Sage notebook, and I think it would be convenient if > math typesetting is available for input (like in mathematica), as it'll make > it

Re: [sage-devel] Re: Basing new development versions of Sage on the previous development version

On Sun, Mar 18, 2012 at 5:45 AM, Jeroen Demeyer wrote: > On 2012-03-17 14:39, Keshav Kini wrote: >> If you instead tell people to base >> their patches on the stable release > I certainly don't want this. > >> Why do patches need to be based on the latest dev release? What do you mean by this que

Re: [sage-devel] Re: Basing new development versions of Sage on the previous development version

On 2012-03-17 14:39, Keshav Kini wrote: > If you instead tell people to base > their patches on the stable release I certainly don't want this. > Why do patches need to be based on the latest dev release? To reduce the change of merge conflicts or doctest conflicts (one patch causing a doctest to

[sage-devel] Re: Math typesetting for inputs in the notebook

2012-03-18 07:46, Yukun skrev: I played around with the Sage notebook, and I think it would be convenient if math typesetting is available for input (like in mathematica), as it'll make it much easier to input long and complicated functions. I will not take part in the GSOC discussion, so this

[sage-devel] Re: GSoC 2012 Kick-off

Hi, you might also want to work on better integrating CVXOPT into Sage. Currently very little of its functionality is exposed in Sage. (let's move this thread to sage-gsoc, by the way) Dmitrii On Saturday, 17 March 2012 18:32:57 UTC+8, Animesh Garg wrote: > > Hello Nathann and Team, > > Greeti

[sage-devel] Re: Math typesetting for inputs in the notebook

For most people in this group, "math typesetting" means TeX/LaTeX typesetting. It is a de fact standard among mathematicians. Then, math notation is typically much less verbose than code in programming language. E.g. the integral sign might mean different things, depending on context. Then, it n