[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h
Martin v. Löwis
report at bugs.python.org
Fri Jan 8 21:10:15 CET 2010
Martin v. Löwis <martin at v.loewis.de> added the comment:
> As far as I can see, the only possible shortcoming of the patch is
> that it restores the current behavior with a 2-way fat ppc/i386 build
> with 10.4u (i.e. the way python.org installers are currently built);
> that is, you would still not be able to use "arch" to select
> PPC-emulation on an Intel machine when a 10.4 SDK build is installed
> on a 10.5 or later Intel system. That's no different than what we
> have today and I don't know of any demand for that feature. There
> are other fairly easy ways around it, if really necessary.
For users, what matters are really the binaries provided by python.org
(and those provided by Apple). So if you restore the previous behavior,
that's basically "for good" - that you still have the compile option to
support arch won't matter for users.
Now, ISTM that users do indeed request the ability to chose between a
32-bit interpreter and a 64-bit interpreter at launch time. I know that
they do on Windows (just because you can), and I would be puzzled if
there weren't OSX users that wanted it one way or the other (depending
on the application you intend to run).
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list