On May 4, 2005, at 7:55 PM, David Reed wrote:
> > On May 4, 2005, at 7:30 PM, Bob Ippolito wrote: > > >> As far as friends scaring you off.. I dunno, maybe they didn't know >> what they were doing when they tried it, or they were bitten by some >> problem that has been solved long since. The only "incompatibility" >> with framework builds is that stupid extensions that don't use >> distutils in their build procedure aren't going to work out of the >> box, but they're probably not going to work out of the box anyway >> because Mac OS X's linker takes different options. > > > On a slightly related note, can I add third-party python modules to > the framework using the standard Unix install process. For example, > I'm using to installing Python modules on Linux using: > python setup.py install Very likely to work, but the module may not be compatible with Mac OS X at all. > or occasionally ./configure;make;make install Less likely, but maybe. It's a bug if any Python extensions use autoconf to build themselves. They should be using distutils. These extensions probably don't work at all on Mac OS X in the first place. -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
