In article <aanlktim-ncqjmc1_kcmj4qp786j1ucq=d2npiu6+u...@mail.gmail.com>, David Cortesi <davecort...@gmail.com> wrote:
> well, this was interesting, I didn't know about arch. As you supposed, > running python3 produces a Python process that Activity Monitor says is > "Intel (64 bit)". > > However, arch -i386 python3 produces exactly the same thing as I get using > arch -x86_64, namely, an Intel(64 bit) process (and loading the same > _tkinter.so). Hmmm. This would suggest there is only the one architecture > defined in its binary? > > applying otool -L to the _tkinter.so that python3 is loading reports > "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Tcl" and etc, so > indeed, the Apple Tcl is baked into the dynamic load lib distributed with > Python3. > > I cannot find any other version of _tkinter.so that might have been > installed by ActiveTcl. So I'm pretty baffled, as well as disappointed that > there's been no response in the ActiveState "support" forum. Ah, sorry, I forgot this was 3.1: unless the ActiveState people backported some stuff from the upcoming Python 3.2, the "arch" trick won't work on OS X 10.6 to select between 32-bit and 64-bit modes. Check the framework bin directory (/Library/Frameworks/Python.framework/Versions/3.1/bin) for something like a python3-32 executable and, if found, try using that. -- Ned Deily, n...@acm.org _______________________________________________ Tkinter-discuss mailing list Tkinter-discuss@python.org http://mail.python.org/mailman/listinfo/tkinter-discuss
