Q: Making Python use no shared extension modules?

[Michael Kent]

simoninusa2001 at yahoo.co.uk (simo) wrote in message news:<30260531.0406101310.65489ea7 at posting.google.com>...
> I don't think you can do it.
> 
> The closest you'd get is McMillan Installer's --onefile which
> basically zips up all the modules into one file, which decompressed on
> the fly when run, although when I've tried it on clean Linux boxes, it
> still requires non-Python stuff (like a wxPython app still requires
> wxTGK installed).

Thanks for the reponse, but let's make sure we are talking about the
right problem.

I know that I can put '*static*' in Modules/Setup, which will cause
all of the extension modules build via the Setup mechanism to be
staticly-linked to the Python executable.  That's what I'm after, but
it requires me to specifically turn-on each extension module that I
want staticly-linked.  What I'm really after is some sort of configure
option that says "universally build all extension modules so that they
will be staticly-linked into the Python executable, build NO shared
libraries".  You would think such an option exists.  You would think
it was '--disable-shared'.  But this does not seem to be the case.