On Mon, Jun 3, 2013 at 3:47 PM, Daniel Holth <dho...@gmail.com> wrote:
> That would make sense. Can you come up with code to detect that a > newly compiled extension is universal, and that a Python is? It looks like distutils.util.get_platform() now does the right thing for knowing what the currently running pyton is (see Ronald's message) For determining the status of a newly compiled extension, I usually simple run the "file" command line utility on it: $ file python python: Mach-O universal binary with 2 architectures python (for architecture ppc): Mach-O executable ppc python (for architecture i386): Mach-O executable i386 (works for *.so, too...) that could easily be parsed out, but we would still want to know the deployment target, which maybe you could get by parsing otool output: $ otool -L python python (architecture ppc): /Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.0) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 47.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.10) python (architecture i386): /Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.10) (compatibility version of libSystem???) But I imagine there is a cleaner way -- Ronald?? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig