On 14 February 2013 05:29, Terry Reedy <tjre...@udel.edu> wrote: > On 2/13/2013 9:38 PM, Rex Macey wrote: >> >> I am sure I have python installed. I have been running it. in command >> line the window title is c:\python33\python.exe. The first line >> begins Python 3.3.0. Later in the line is the string "64 bit <AMD64>] >> on Win32".
I don't know why you feel the need to paraphrase this information rather than simply paste the interpreter message into the email. The latter would be more useful for others trying to help understand your problem. >> Thus it appears I am trying to run a 32bit numpy with a 64bit python. >> (Seems like a big ole 64 bit python should be able to swallow a >> little 32 bitty numpy). Is there a 64bit numpy? If not why not? Because numpy/scipy make extensive use of Python's underlying binary interfaces. These are incompatible between 32 and 64 bit Python. > Ask the numpy people. I am surprised since a reason to be using 64 rather > than 32 bit python is to have objects larger than 2 gigabytes and memory > larger than 4 gigabytes. Numerical/scientific programming is relatively > likely to need such. Yes but most people who are doing that sort of thing would just compile their own numpy/scipy and probably wouldn't be using Windows for the their main computations anyway. Numpy does work on 64 bit Python but official binaries are not distributed via the sourceforge page. Unofficial binaries are available here: http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy >> someone get on this? Seriously, I'm under the impression that I need >> the 64 bit python because I have a 64 bit OS. I don't know about Windows 8 but I've used 32 bit Python on 64 bit XP no problem. My impression was that 64 bit Windows (unlike OSX and most Linux distros) ships with 32 bit duplicates of all its libraries so that it can run 32 bit applications without modification. My Windows usage significantly predates Windows 8, though so this may have changed some time ago. Oscar -- http://mail.python.org/mailman/listinfo/python-list