Bill.
Oh. Is it easy to use my own copy of Sage in SMC? Brief how-to? #
Bill.
On Mon, Apr 27, 2015 at 7:33 AM, Bill Page <bill...@newsynthesis.org> wrote:
> On 27 April 2015 at 10:31, Bill Page <bill...@newsynthesis.org> wrote:
>> On 27 April 2015 at 10:23, Dima Pasechnik <dim...@gmail.com> 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 test?
>>>
>>>
>>> fricas interface is in Python, so you would just have to run 'sage -b', in a
>>> "normal"
>>> Sage setting; and this is almost instant. (E.g. if you use your own copy of
>>> Sage in an SMC project).
>>>
>>
>> Oh. Is it easy to use my own copy of Sage in SMC? Brief how-to?
>>
>
> OK, from a teminal session I know. But how to use my own copy of Sage
> from a Sage Notebook in SMC?
See
https://github.com/sagemath/cloud/wiki/FAQ#-question-i-want-to-use-my-own-sage-binary-takes-2-minutes
On Monday, 27 April 2015 15:36:17 UTC+1, William Stein wrote:On Mon, Apr 27, 2015 at 7:33 AM, Bill Page <bill...@newsynthesis.org> wrote:
> On 27 April 2015 at 10:31, Bill Page <bill...@newsynthesis.org> wrote:
>> On 27 April 2015 at 10:23, Dima Pasechnik <dim...@gmail.com> 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 test?
>>>
>>>
>>> fricas interface is in Python, so you would just have to run 'sage -b', in a
>>> "normal"
>>> Sage setting; and this is almost instant. (E.g. if you use your own copy of
>>> Sage in an SMC project).
>>>
>>
>> Oh. Is it easy to use my own copy of Sage in SMC? Brief how-to?
>>
>
> OK, from a teminal session I know. But how to use my own copy of Sage
> from a Sage Notebook in SMC?
See
https://github.com/sagemath/cloud/wiki/FAQ#-question-i-want-to-use-my-own-sage-binary-takes-2-minutes
the URL to download the binary is outdated there.the linkdoes not give any UW locations (even no USA locations!), so it's going to be a slower download...
On Mon, Apr 27, 2015 at 8:11 AM, Dima Pasechnik <dim...@gmail.com> 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 bandwidth on Google, and it cost over $50 in one day. So
that's not an option right now. Maybe a different hosting provider
would work for that purpose.
Bill.
On Mon, Apr 27, 2015 at 9:14 AM, Dima Pasechnik <dim...@gmail.com> wrote:
>
>
> On Monday, 27 April 2015 17:00:26 UTC+1, help wrote:
>>
>> On Mon, Apr 27, 2015 at 8:11 AM, Dima Pasechnik <dim...@gmail.com> 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 bandwidth on Google, and it cost over $50 in one day. So
>> that's not an option right now. Maybe a different hosting provider
>> would work for that purpose.
>
>
> github does allow binary downloads within their releases.
> Not sure whether one can host much this way, but perhaps
> a couple of gigabytes is possible.
>
That's a great idea! It seems to solve the problem completely. See
https://help.github.com/articles/distributing-large-binaries/
which says:
"We don't limit the total size of your binary release files, nor
the bandwidth used to deliver them. However, each individual file must
be under 1GB in size."
On 27 April 2015 at 12:31, Dima Pasechnik <dim...@gmail.com> 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/Sage worksheet?
>
> IMHO the problem is actually in axiom.py, where eval stuff is defined.
> fricas interface inherits from there.
> So you'll have to modify the corresponding function from axiom.py,
> so that it overwrites the one inherited.
>
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/237df92ef4e6b5117654f3a3ff71b4aa10b0aa36#diff-60c84efff9cc620d4d8bbd8110321ffd
On Apr 29, 2015 7:30 AM, "Dima Pasechnik" <dim...@gmail.com> 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 trac extension: http://sagemath.org/doc/developer/git_trac.html#chapter-git-trac,
> but bare git would do, too; you need an account on trac.sagemath.org for this, anyway)
>
> there is also an experimental github way, but I don't really know how it works.
>
Sorry but sage-trac looks like a big hammer for a small nut :)
>
> PS. I can only speak about fricas mode, as I don't have other axiom(s) installed, and cannot test there.
> Can you?
>
No I only have FriCAS installed.
> PPS. if you really are pressed for time, I can submit this patch instead...
>
Thanks I would really appreciate that.
On Apr 29, 2015 7:30 AM, "Dima Pasechnik" <dim...@gmail.com> 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 trac extension: http://sagemath.org/doc/developer/git_trac.html#chapter-git-trac,
> but bare git would do, too; you need an account on trac.sagemath.org for this, anyway)
>
> there is also an experimental github way, but I don't really know how it works.
>Sorry but sage-trac looks like a big hammer for a small nut :)
>
> PS. I can only speak about fricas mode, as I don't have other axiom(s) installed, and cannot test there.
> Can you?
>No I only have FriCAS installed.
> PPS. if you really are pressed for time, I can submit this patch instead...
>Thanks I would really appreciate that.
On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote:
On Apr 29, 2015 7:30 AM, "Dima Pasechnik" <dim...@gmail.com> 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 trac extension: http://sagemath.org/doc/developer/git_trac.html#chapter-git-trac,
> but bare git would do, too; you need an account on trac.sagemath.org for this, anyway)
>
> there is also an experimental github way, but I don't really know how it works.
>Sorry but sage-trac looks like a big hammer for a small nut :)
>
> PS. I can only speak about fricas mode, as I don't have other axiom(s) installed, and cannot test there.
> Can you?
>No I only have FriCAS installed.
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.
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, 2014 at
23:34:17 "\r\n'
%axiom
)version
Value = "Axiom Axiom (May 2012) built on Friday July 25, 2014 at 23:34:17 "
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 things this way. It just occurred to me that for such
simple things there should be simple solutions. And I guess there is:
find some else to do it. I am serious that perhaps this is not such a
bad thing provided of course that there are enough people willing to
do this.