Thanks for the pointer. Alas, I get the same error when I run the
notebook(interface="mini addr") from my laptop. This looks like something
on my LAN is blocking access. I'll fuss some more with it.
On Fri, Aug 12, 2011 at 10:21 PM, Benjamin Jones
wrote:
> On Aug 12, 10:47 pm, Owen Densmore
On Aug 12, 9:38 pm, Santanu Sarkar
wrote:
> I have 64 bit integer N. I want to rotate bits of N cyclically 5 bits right
> and 5 bits left to generate two integers N1, N2.
> How can I do this in Sage efficiently?
See section 5.4.1 of:
http://docs.python.org/library/stdtypes.html
--
BFJ
--
To
On Aug 12, 10:47 pm, Owen Densmore wrote:
> Now I'd like to access the Mini from my other systems on the same LAN. If I
> tryhttp://10.0.1.222(where 10.0.1.222 is the Mini's address) from them, I
> get access to the Apache server, as expected. However, when I then try
> accessing port 8000 (htt
I've a Mac Mini on a LAN (AirPort) with a recent Sage install using the
Sage.app 64 bit distro. I've set Web Sharing on.
The Sage.app launches the notebook service
on http://localhost:8000/home/admin/ as documented.
Now I'd like to access the Mini from my other systems on the same LAN. If I
I have 64 bit integer N. I want to rotate bits of N cyclically 5 bits right
and 5 bits left to generate two integers N1, N2.
How can I do this in Sage efficiently?
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+un
On 8/12/11 10:42 AM, samontab wrote:
Thanks for the suggestions.
sage forker works fine on my machine. The startup of sage is almost
instant now. I have a problem though. Normally I would call sage
scripts like this:
sage script.sage
I tried using fsage for executing the scripts:
./fsage scri
Thanks for the suggestions.
sage forker works fine on my machine. The startup of sage is almost
instant now. I have a problem though. Normally I would call sage
scripts like this:
sage script.sage
I tried using fsage for executing the scripts:
./fsage script.sage
But it only starts sage (very
FIXED: I was suspecting something was corrupted, or there was
permission problems.
I ended up moving my sage_notebook.sagenb out, which was then re-
created. Everything was fine then: I then just copied over what was in
the user folder for each wb, and I'm back in business!
On Aug 8, 7:28 pm, Rya
On 11 Aug., 22:40, Rado wrote:
> click "publish" again and you should see a button "stop publishing".
Yes, it is a bit like on Windows, when you have to click the "start"
button in order to shut down your computer...
--
To post to this group, send email to sage-support@googlegroups.com
To unsub
