On 2010-11-26, at 7:24 PM, Ned Deily wrote: >> >> I certainly don't see the -32/-64 binaries in ActivePython 3.1.2.4 >> (based on Python 3.1.2). So if 3.1.2 is supposed to generate these - >> then this is an ActivePython bug that needs to be fixed. > > As I noted earlier, 32-bit/64-bit 3.1 (and 2.6, for that matter) builds > do not support architecture selection via the arch command on 10.6, > which will always prefer to launch 64-bit if possible. A feature was > added to 2.7 and 3.2 to support this. For 2.6 and 3.1 systems, the > standard ./configure options --with-universal-archs="3-way", "intel" or > "all" create the separate 32- and -64-bit executables. Running on 10.6 > you can see the problem with the ActivePython 3.1.2.4 - it always runs > in 64-bit mode:
Ok, thanks for this background information. Strangely enough, when I now build ActivePython 3.1.3.5 (to be released by end of this week), I see the -32/-64/-all binaries. It was only missing from the 3.1.2.4 build (was it because of having 3.1.2.3 - ppc+i386 - in /Lib/Frmwrk?). Using the same build: $ python3.1-64 -c 'import sys;print(sys.maxsize)' 9223372036854775807 $ python3.1-32 -c 'import sys;print(sys.maxsize)' 2147483647 Further I will also update the FAQ <http://goo.gl/zGD3T>, which is incorrectly suggesting `arch` for 2.6 and 3.1 too. -srid _______________________________________________ Tkinter-discuss mailing list Tkinter-discuss@python.org http://mail.python.org/mailman/listinfo/tkinter-discuss
