On Nov 2, 2007, at 3:38 PM, Martina Oefelein wrote: > > Am 02.11.2007 um 08:03 schrieb Ronald Oussoren: > >> As you've noticed the actual framework is 64bit but the commandline >> tools are not. It should be easy enough to add 64-bit command-line >> tools as well, but even then you'll have to add extra arguments to >> build 64-bit extensions (as Boyd mentions). > > I think this actually makes sense: if the command line tools were > 32/64 bit universal, scripts would run with the 64 bit version on 64 > bit systems, and wouldn't be able to use any of the libraries that > are only 32 bit. > > The framework, on the other hand, should be 32/64 bit universal so > that both 32 and 64 bit applications can embed python. >
That's where I'm missing info on the other ways Python can be used. So another package links 64bit to the python framework, but it still has to run from some python interpreter executable that is embedded - where does that interpreter come from, if not the one in the framework bundle? ----- William Kyngesburye <kyngchaos*at*kyngchaos*dot*com> http://www.kyngchaos.com/ "This is a question about the past, is it? ... How can I tell that the past isn't a fiction designed to account for the discrepancy between my immediate physical sensations and my state of mind?" - The Ruler of the Universe _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
