From: Kevin K. <ka...@so...> - 2011-11-28 18:23:50
|
I have, sadly, had to remove 32-bit Python from my machine, thus breaking Vpython. I had another package that I had to use for my research that only was too difficult to reconfigure to compile to 32-bit Python on a 64-bit machine. So I needed 64-bit Python to do my work. So I've had to give up on Vpython for my own use (though my son will still use it on the household computer, which does not need to run research code and can tolerate using 32-bit Python). I suppose, that with considerable effort I could dig up an old version of Python that could be compiled for a 32-bit machine, but the hassle involved is too large. Having both a 32-bit and 64-bit version of Python 2.7.2 on the same Mac seems to be very difficult to set up, as the Mac method for having multiple versions of python seems to rely on the version number to keep the directories straight. Unless the 32-bit kluge is fixed within the next year, Vpython will become just another good idea that disappeared because it was tied to obsolete technology. I suspect that Vpython will almost disappear within 3-5 years if it remains tied to legacy computers. Kevin Karplus |