On 30 April 2015 at 21:45, kcrisman wrote:
> Bill Page wrote:
>> It just occurred to me that for such
>> simple things there should be simple solutions. And I guess there is:
>
> Well, that has been discussed a lot. There *is* one possibility now - you
> can open a pull request at https://githu
>
> Yes, I guess we do so at our own risk. :) My intention was not to
> flame but rather just expressing my reaction after reading
>
> http://sagemath.org/doc/developer/git_trac.html#chapter-git-trac
>
> and considering the possible fate of my 3 line patch if I don't find
> the time to do thin
On Thu, Apr 30, 2015 at 2:52 PM, Bill Page wrote:
>> I won't claim that Sage's
>> doctests make Sage have "fewer errors or problems" than the other
>> systems you use (they surely have their own approaches to testing).
>> However, I absolutely claim -- and I'm sure anybody with nontrivial
>> Sage
On 30 April 2015 at 16:06, William Stein wrote:
> On Thu, Apr 30, 2015 at 12:34 PM, Bill Page
> wrote:
>> ...
> You stated 'that the Sage developer emphasis on "doc tests" has
> resulted in any fewer errors or problems in Sage in comparison to
> other systems.' I'm not sure if I should respon
On Thu, Apr 30, 2015 at 12:34 PM, Bill Page wrote:
> On 30 April 2015 at 13:34, Dima Pasechnik wrote:
>> On Thursday, 30 April 2015 17:11:39 UTC+1, Bill Page wrote:
>> ...
>> well, for rants we have a special newsgroup called sage-flame.
>>
>
> Yes, although I consider what I wrote more of an inc
On 30 April 2015 at 13:29, Dima Pasechnik wrote:
> On Thursday, 30 April 2015 18:12:00 UTC+1, Bill Page wrote:
>>
>> I just tested the patch and now I get the following in a Sage worksheet on
>> SMC:
>>
>> axiom.eval(")version")
>>
>> 'alue = "Axiom Axiom (May 2012) built on Friday July 25, 2014 a
On 30 April 2015 at 13:34, Dima Pasechnik wrote:
> On Thursday, 30 April 2015 17:11:39 UTC+1, Bill Page wrote:
> ...
> well, for rants we have a special newsgroup called sage-flame.
>
Yes, although I consider what I wrote more of an inconvenient
statement of fact so maybe I used the wrong tag.
>
On Thursday, 30 April 2015 17:11:39 UTC+1, Bill Page wrote:
>
> On 30 April 2015 at 05:29, Dima Pasechnik >
> wrote:
> > On Thursday, 30 April 2015 10:09:55 UTC+1, Dima Pasechnik wrote:
> >> On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote:
> >>>
> >>> > PPS. if you really are pre
On Thursday, 30 April 2015 18:12:00 UTC+1, Bill Page wrote:
>
> I just tested the patch and now I get the following in a Sage worksheet on
> SMC:
>
> axiom.eval(")version")
>
> 'alue = "Axiom Axiom (May 2012) built on Friday July 25, 2014 at 23:34:17
> "\r\n'
>
> %sage
> from axiom import a
I just tested the patch and now I get the following in a Sage worksheet on SMC:
axiom.eval(")version")
'alue = "Axiom Axiom (May 2012) built on Friday July 25, 2014 at 23:34:17 "\r\n'
%sage
from axiom import axiom
axiom.eval(")version")
'Value = "Axiom Axiom (May 2012) built on Friday July 25,
On 30 April 2015 at 05:29, Dima Pasechnik wrote:
> On Thursday, 30 April 2015 10:09:55 UTC+1, Dima Pasechnik wrote:
>> On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote:
>>>
>>> > PPS. if you really are pressed for time, I can submit this patch
>>> > instead...
>>> >
>>>
>>> Thanks I wou
On 30 April 2015 at 05:29, Dima Pasechnik wrote:
> ...
>>
>> I thought that on SMC in a Sage worksheet you can do %axiom
>> and this will call a system-wide Axiom. Currently SMC is hanging for me,
>> so I can't check.
>
>
> OK, one can start axiom in an SMC terminal, by typing axiom
> it is
> (1)
On Thursday, 30 April 2015 10:09:55 UTC+1, Dima Pasechnik wrote:
>
>
>
> On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote:
>>
>>
>> On Apr 29, 2015 7:30 AM, "Dima Pasechnik" wrote:
>>
>> >> >
>> >> > this patch should go into Sage proper, as it also fixes the same as
>> with SMC
>>
On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote:
>
>
> On Apr 29, 2015 7:30 AM, "Dima Pasechnik" >
> wrote:
>
> >> >
> >> > this patch should go into Sage proper, as it also fixes the same as
> with SMC
> >> > issue with Sage's notebook.
> >> >
> >>
> >> Sure. What is the best
On Apr 29, 2015 7:30 AM, "Dima Pasechnik" wrote:
>> >
>> > this patch should go into Sage proper, as it also fixes the same as
with SMC
>> > issue with Sage's notebook.
>> >
>>
>> Sure. What is the best way to make that happen?
>
> the usual way is via trac.sagemath.org
> (for instance using git
On Tuesday, 28 April 2015 21:17:43 UTC+1, Bill Page wrote:
>
> On 27 April 2015 at 23:52, Dima Pasechnik >
> wrote:
> >
> > On Tuesday, 28 April 2015 02:27:21 UTC+1, Bill Page wrote:
> >>
> >> Yes you are right. The problem was in the original axiom.py. Here is a
> >> patch that corrects th
On 27 April 2015 at 23:52, Dima Pasechnik wrote:
>
> On Tuesday, 28 April 2015 02:27:21 UTC+1, Bill Page wrote:
>>
>> Yes you are right. The problem was in the original axiom.py. Here is a
>> patch that corrects the problem:
>>
>> https://github.com/billpage/sage/commit/237df92ef4e6b5117654f3a3ff7
On Tuesday, 28 April 2015 02:27:21 UTC+1, Bill Page wrote:
>
> On 27 April 2015 at 12:31, Dima Pasechnik >
> wrote:
> > ...
> > On Monday, 27 April 2015 17:23:50 UTC+1, Bill Page wrote:
> >>
> >> On the original point of this thread: Is there anything wrong with
> >> just grabbing the 'fri
On 27 April 2015 at 12:31, Dima Pasechnik wrote:
> ...
> On Monday, 27 April 2015 17:23:50 UTC+1, Bill Page wrote:
>>
>> On the original point of this thread: Is there anything wrong with
>> just grabbing the 'fricas.py' source from somewhere, changing it,
>> and then importing it into an SMC/Sag
On Monday, 27 April 2015 17:39:56 UTC+1, Dima Pasechnik wrote:
>
>
>
> On Monday, 27 April 2015 17:18:09 UTC+1, help wrote:
>>
>> On Mon, Apr 27, 2015 at 9:14 AM, Dima Pasechnik
>> wrote:
>> >
>> >
>> > On Monday, 27 April 2015 17:00:26 UTC+1, help wrote:
>> >>
>> >> On Mon, Apr 27, 2015 a
On Monday, 27 April 2015 17:18:09 UTC+1, help wrote:
>
> On Mon, Apr 27, 2015 at 9:14 AM, Dima Pasechnik > wrote:
> >
> >
> > On Monday, 27 April 2015 17:00:26 UTC+1, help wrote:
> >>
> >> On Mon, Apr 27, 2015 at 8:11 AM, Dima Pasechnik
> wrote:
> >> >> That won't be available for long.
On Monday, 27 April 2015 17:23:50 UTC+1, Bill Page wrote:
>
> On 27 April 2015 at 12:00, William Stein > wrote:
> > ...
> > SMC won't be able to provide that sort of hosting for free, that's for
> sure.
> >
> >> I think new projects will have enough room.
> >
> > As of right now they do.
On 27 April 2015 at 12:00, William Stein wrote:
> ...
> SMC won't be able to provide that sort of hosting for free, that's for sure.
>
>> I think new projects will have enough room.
>
> As of right now they do. However, I have to move everything out of
> UW asap, so I can't promise anything at al
On Mon, Apr 27, 2015 at 9:14 AM, Dima Pasechnik wrote:
>
>
> On Monday, 27 April 2015 17:00:26 UTC+1, help wrote:
>>
>> On Mon, Apr 27, 2015 at 8:11 AM, Dima Pasechnik wrote:
>> >> That won't be available for long.
>> >
>> >
>> > how about having an SMC-only filestore or an http server for this k
On Monday, 27 April 2015 17:00:26 UTC+1, help wrote:
>
> On Mon, Apr 27, 2015 at 8:11 AM, Dima Pasechnik > wrote:
> >> That won't be available for long.
> >
> >
> > how about having an SMC-only filestore or an http server for this kind
> of
> > things?
> > (just to save bandwidth...)
>
>
On Mon, Apr 27, 2015 at 8:11 AM, Dima Pasechnik wrote:
>> That won't be available for long.
>
>
> how about having an SMC-only filestore or an http server for this kind of
> things?
> (just to save bandwidth...)
Maybe later -- I don't know. Harald tried posting binaries and paying
for the bandwi
it seems that the current SMC quota settings do not allow this on an
ordinary project.
At least I was unable to untar the sage binary into a relatively empty
project
(project id: 42c646bc-c7fc-41d8-b50d-efc995e3cd08)
On Monday, 27 April 2015 15:36:18 UTC+1, William wrote:
>
> On Mon, Apr 27, 20
On Monday, 27 April 2015 16:00:15 UTC+1, help wrote:
>
> On Mon, Apr 27, 2015 at 7:53 AM, Dima Pasechnik > wrote:
> >
> >
> > On Monday, 27 April 2015 15:46:27 UTC+1, Dima Pasechnik wrote:
> >>
> >>
> >>
> >> On Monday, 27 April 2015 15:36:17 UTC+1, William Stein wrote:
> >>>
> >>> On M
On Monday, 27 April 2015 15:53:59 UTC+1, Dima Pasechnik wrote:
>
>
>
> On Monday, 27 April 2015 15:46:27 UTC+1, Dima Pasechnik wrote:
>>
>>
>>
>> On Monday, 27 April 2015 15:36:17 UTC+1, William Stein wrote:
>>>
>>> On Mon, Apr 27, 2015 at 7:33 AM, Bill Page
>>> wrote:
>>> > On 27 April 2015 a
On Mon, Apr 27, 2015 at 7:53 AM, Dima Pasechnik wrote:
>
>
> On Monday, 27 April 2015 15:46:27 UTC+1, Dima Pasechnik wrote:
>>
>>
>>
>> On Monday, 27 April 2015 15:36:17 UTC+1, William Stein wrote:
>>>
>>> On Mon, Apr 27, 2015 at 7:33 AM, Bill Page
>>> wrote:
>>> > On 27 April 2015 at 10:31, Bill
On Monday, 27 April 2015 15:46:27 UTC+1, Dima Pasechnik wrote:
>
>
>
> On Monday, 27 April 2015 15:36:17 UTC+1, William Stein wrote:
>>
>> On Mon, Apr 27, 2015 at 7:33 AM, Bill Page
>> wrote:
>> > On 27 April 2015 at 10:31, Bill Page wrote:
>> >> On 27 April 2015 at 10:23, Dima Pasechnik wr
On Monday, 27 April 2015 15:36:17 UTC+1, William Stein wrote:
>
> On Mon, Apr 27, 2015 at 7:33 AM, Bill Page > wrote:
> > On 27 April 2015 at 10:31, Bill Page > wrote:
> >> On 27 April 2015 at 10:23, Dima Pasechnik > wrote:
> >>>
> >>> On Monday, 27 April 2015 15:00:30 UTC+1, Bill Page wro
On Monday, 27 April 2015 15:31:50 UTC+1, Bill Page wrote:
>
> On 27 April 2015 at 10:23, Dima Pasechnik >
> wrote:
> >
> > On Monday, 27 April 2015 15:00:30 UTC+1, Bill Page wrote:
> >> ...
> >> What's a good way to debug the fricas interface in SageMathCloud? Can
> >> I just copy and then
On Mon, Apr 27, 2015 at 7:33 AM, Bill Page wrote:
> On 27 April 2015 at 10:31, Bill Page wrote:
>> On 27 April 2015 at 10:23, Dima Pasechnik wrote:
>>>
>>> On Monday, 27 April 2015 15:00:30 UTC+1, Bill Page wrote:
...
What's a good way to debug the fricas interface in SageMathCloud? C
On 27 April 2015 at 10:31, Bill Page wrote:
> On 27 April 2015 at 10:23, Dima Pasechnik wrote:
>>
>> On Monday, 27 April 2015 15:00:30 UTC+1, Bill Page wrote:
>>> ...
>>> What's a good way to debug the fricas interface in SageMathCloud? Can
>>> I just copy and then import the code into a workshe
On 27 April 2015 at 10:23, Dima Pasechnik wrote:
>
> On Monday, 27 April 2015 15:00:30 UTC+1, Bill Page wrote:
>> ...
>> What's a good way to debug the fricas interface in SageMathCloud? Can
>> I just copy and then import the code into a worksheet? I.e. avoid
>> having to rebuild Sage just to te
On Monday, 27 April 2015 15:00:30 UTC+1, Bill Page wrote:
>
> On 27 April 2015 at 00:20, William Stein > wrote:
> > On Sun, Apr 26, 2015 at 7:49 PM, Bill Page > wrote:
> >>
> >> OK, thanks. Any pointers to documentation of "modes" in the Sage
> >> worksheet would be fine too.
> >
> > The
On 27 April 2015 at 00:20, William Stein wrote:
> On Sun, Apr 26, 2015 at 7:49 PM, Bill Page wrote:
>>
>> OK, thanks. Any pointers to documentation of "modes" in the Sage
>> worksheet would be fine too.
>
> There's no documentation yet. However, you might find this example
> worksheet useful:
>
On Sun, Apr 26, 2015 at 7:49 PM, Bill Page wrote:
> On 26 April 2015 at 20:49, William Stein wrote:
>> On Sun, Apr 26, 2015 at 5:40 PM, Bill Page
>> wrote:
>> ...
>>> Is there a way to tell the worksheet to render code
>>> between $$ ... $$ as MathJax or have MathML markup rendered by
>>> the
On 26 April 2015 at 20:49, William Stein wrote:
> On Sun, Apr 26, 2015 at 5:40 PM, Bill Page wrote:
> ...
>> Is there a way to tell the worksheet to render code
>> between $$ ... $$ as MathJax or have MathML markup rendered by
>> the browser instead of being treated simply as text?
>
> You'll ha
40 matches
Mail list logo
