Author loewis
Recipients cfriedt, hanwen, janneke-sf, lkcl, loewis, nzjrs, rmt38, rwmjones, scott.tsai
Date 2008-10-07.19:49:26
SpamBayes Score 2.95987e-07
Marked as misclassified No
Message-id <>
In-reply-to <>
> the compiling strategy for Python (IIRC) is to compile everything,
> including modules that will never work, and use compiler errors as a
> signal to not include a module in the result. 

I don't think this can work in the cross-compilation case, though
(or the entire part of it can't really work). It uses the
target's python binary to run, compiles the modules, and then
tries to load them. In a cross-compilation case, you can't run the
target python binary, and even if you use a host python instead, you
can't load the target extension modules (unless the "cross" compilation
is for the same microprocessor and operating system - a case I'm not
very much interested in).
Date User Action Args
2008-10-07 19:49:27loewissetrecipients: + loewis, lkcl, hanwen, janneke-sf, rmt38, scott.tsai, nzjrs, cfriedt, rwmjones
2008-10-07 19:49:26loewislinkissue1597850 messages
2008-10-07 19:49:26loewiscreate