which sage should i download for evaluation purposes on Snow Leopard?

[Anthony Durity]

Hi Sage people,

Scenario: clean install

I have the sage-4.8-OSX-64bit-10.6-x86_64-Darwin-app.dmg but it's
giving me the following error ...

Last login: Wed Apr 4 17:05:00 on ttys003
'/Applications/Sage-4.8-OSX-64bit-10.6.app/Contents/Resources/sage'/sage
--notebook
device-b72924:~ jollyrotten$
'/Applications/Sage-4.8-OSX-64bit-10.6.app/Contents/Resources/sage'/sage
--notebook
Traceback (most recent call last):
File "/Applications/Sage-4.8-OSX-64bit-10.6.app/Contents/Resources/sage/local/bin/sage-notebook",
line 3, in <module>
import os, sys, socket
File "/Applications/Sage-4.8-OSX-64bit-10.6.app/Contents/Resources/sage/local/lib/python/socket.py",
line 46, in <module>
import _socket
ImportError: No module named _socket
device-b72924:~ jollyrotten$

Any suggestions?

Thanks!

I have 32 bit Snow Leopard but I thought that I could run 64 bit apps,
I can, can't I?

Regards,
Anthony

[David Roe]

You can't run a 64-bit build on a 32-bit machine.  I don't think that there's a pre-build binary for 32-bit Snow Leopard, so you'll need to build it from source.
David

--
To post to this group, send an email to sage-...@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[Justin C. Walker]

On Apr 4, 2012, at 10:03 , Anthony Durity wrote:

> Hi Sage people,
>
> Scenario: clean install

[snip]

> I have 32 bit Snow Leopard but I thought that I could run 64 bit apps,
> I can, can't I?

What hardware system are you using. As David said, you can't run 64-bit software on 32-bit hardware, but you can run 64-bit software on 64-bit hardware even if your OS (Kernel) is running in 32-bit mode.

So, for 10.6, it's the hardware that dictates whether you can run 64-bit software.

Justin

--
Justin C. Walker, Curmudgeon-at-Large
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email

[Georg S. Weber]

ImportError: No module named _socket

That sort of breakage should be fixed by the OS X ...-app.p0.dmg's (note the "p0") --- there was a trac a trac ticket and several discussions. I don't think it has something to do with the bitness, i.e. 32 vs. 64. Did you really use an older dmg "without the p0"? If so, please test a newer "p0" one --- and please tell us the outcome, we had big trouble in reproducing what you (and many others) reported.
(If you really have one of the very first Intel Macs (with a "Core Solo" or a "Core Duo" CPU), then you'll probably have to use a ...32bit... Sage. Otherwise, ...64bit... should be fine .)


Cheers,
Georg

[Anthony Durity]

To be very clear about this to avoid confusion.

I have a white Macbook about 3 years old, designated a Macbook5,2
http://www.everymac.com/systems/apple/macbook/specs/macbook-core-2-duo-2.13-white-13-mid-2009-nvidia-specs.html

It's got 2ghz Core 2 duo so it's definitely got a 64bit cpu as in it
would run 64 bit Linux no bother but I'm running Snow Leopard in 32
bit mode so the core OS (kernel and extensions) is in 32 bit mode
(boooo).
I can run 64bit apps though so for instance Safar and iTerm are in 64
bits so that's why I downloaded the 64 version (dmg) of Sage.

I don't really see how this relates to the error. Maybe until these
issues are ironed out it would be better if Sage released one version
(a 32 bit one) for MacOSX that installs without a hitch and runs
without any faffing about. There's no need to over-complicate things
and as it is the users first impression of Sage it is important. Don't
get me wrong at all, I don't mind personally, just trying to give
helpful advice.

Which version should I download by the way? Could you give me a link?

Thanks.

2012/4/4 Georg S. Weber <georg...@googlemail.com>:

[Georg S. Weber]

On Thursday, 5 April 2012 00:44:28 UTC+2, Anthony Durity wrote:

To be very clear about this to avoid confusion.

I have a white Macbook about 3 years old, designated a Macbook5,2
http://www.everymac.com/systems/apple/macbook/specs/macbook-core-2-duo-2.13-white-13-mid-2009-nvidia-specs.html

It's got 2ghz Core 2 duo so it's definitely got a 64bit cpu as in it
would run 64 bit Linux no bother but I'm running Snow Leopard in 32
bit mode so the core OS (kernel and extensions) is in 32 bit mode
(boooo).
I can run 64bit apps though so for instance Safar and iTerm are in 64
bits so that's why I downloaded the 64 version (dmg) of Sage.

I don't really see how this relates to the error. Maybe until these
issues are ironed out it would be better if Sage released one version
(a 32 bit one) for MacOSX that installs without a hitch and runs
without any faffing about. There's no need to over-complicate things
and as it is the users first impression of Sage it is important. Don't
get me wrong at all, I don't mind personally, just trying to give
helpful advice.

Which version should I download by the way? Could you give me a link?

Thanks.

Hi,

I wanted to do this for quite some time, so I did in the past few minutes:
On my MacBook2,1 (for specs see http://www.everymac.com/systems/apple/macbook/specs/macbook-core-2-duo-2.0-white-13-specs.html , it's a bit older than yours, but definitely "the same" for our purpose --- the installed OS X 10.6 Snow Leopard starts up its kernel in 32-bit mode there, unless you press the keys "6" and "4" during startup --- which I did *not* do), I deleted all traces of former Sage installations in my home directory.

Then I went to:

http://www.sagemath.org/download-mac.html

and chose some mirror (in my case "http://sunsite.rediris.es", because I'm in Spain at the moment), then went to

http://sunsite.rediris.es/mirror/sagemath/osx/intel/index.html

and from there downloaded

sage-4.8-OSX-64bit-10.6-x86_64-Darwin-app.p0.dmg

(note both the "64bit/x86_64" and the "p0", and of course "10.6"). I clicked on the dmg, dragged the "Sage" icon (i.e. the application folder, something between 1 GB and 2 GB big) to some folder of my choice (actually under my home dir, but you could choose the general OS X "application" directory as well). It takes some minutes to copy. Then I clicked on the (just copied) Sage "in the file system". Again, this takes quite some time, but ultimately Sage 4.8 starts up, and lets you first enter the new password for your notebok server, to be used by the "admin" account. After that, one stale terminal session hangs around (I think this will happen only for the first time you start Sage), but apart from that, Sage (resp. the Sage app) is now "there" and usable.

Hope that helps,

Georg

[Ivan Andrus]

I'm so glad to hear that!  At least it worked for one person besides me. :-)

If you have the same problem with a "p0" version then I would really like to debug it and fix the root problem.  One thing to note is that if you have had Terminal.app open for a long time then it's possible that it was started by an old buggy Sage.app and that would still cause the problem.  You can either quit Terminal.app completely, and/or check that 

env | grep SAGE

comes back clean.

-Ivan

[Anthony Durity]

Thanks Georg,

This worked a treat. No hitches. Asked me for an admin password,
popped open a browser window after.
Sage does not show up as a 64 bit app in activity monitor by the way ...

Lucky you in beautiful España!
Regards from chilly Ireland,
Anthony

2012/4/5 Georg S. Weber <georg...@googlemail.com>:

[Anthony Durity]

Hi there Ivan,

No problem with a "p0" version it seems. Perhaps this is the only one
that should be offered on mirrors? Thanks for your advice. I don't
know if I had stale processes and whatnot but I noticed before I
reinstalled that there were some sage processes hanging around so I
killed them from the command line before installing p0 thingy. So far
so good now though.

Regards,
Anthony

2012/4/5 Ivan Andrus <darth...@gmail.com>:

[Ivan Andrus]

Anthony,

I'm glad it worked for you. The "p0" version is the only one for download, at least on the Freie Universität Berlin, Germany mirror.

-Ivan

[Georg S. Weber]

 Hi Anthony,

thank you very much for your report!

I just checked all the mirrors, and except for one (" Universidade Federal do Paraná, Brazil") it seems all now provide the "...p0.." app dmg's. It always takes some time to synchronize for all the mirrors. Sorry for the inconvenience!

@Ivan:
It seems also, that almost all the OS X "non-app" (i.e. normal) bdist's have vanished. Was that intentional (maybe there was a misunderstanding in the communcation with Harald)?


Cheers,
Georg

[Ivan Andrus]

That wasn't my intention.  We must have miscommunicated.

-Ivan

[kcrisman]

Yeah, and even for PPC machines, where this was never a problem. Who
would have even created a "p0" for them? We definitely always want to
provide non-app dmgs as well. How were the "p0"s created? I don't
recall seeing that discussion or ticket...

[Ivan Andrus]

There was a discussion on sage-devel [1]. For some reason I thought the problem occurred on PPC machines as well.

All I did to create them was to change one line of start-sage.sh (same effective change as #12161). I didn't rebuild them so there should be absolutely no problems (famous last words) even on PPC. I still wish there were a non-hacky way we could distribute them both on the same dmg. It would simplify things so much.

-Ivan

[1] http://comments.gmane.org/gmane.comp.mathematics.sage.devel/57621