The attached patch adds the ability to distutils to
have extensions stripped from scripts when they are
"built".  This adds an option, --strip-extensions, to
the build_scripts command which defaults to false; the
option is only honored on systems for which os.name ==
"posix" and sys.platform != "darwin".

While I generally like the idea of such a feature,
there are some open issues regarding this:

1.  To support legacy applications which install
scripts with extensions but which want the new option
to apply to more recently added scripts by default,
there needs to be a way to specify this on a per-script
basis.  I've not thought about how to do this yet, but
I'd generally prefer to have this option set in a
setup.cfg file included in a distribution.

2. Mac OS X appearantly still has some issues with the
differences between GUI and non-GUI applications, and
the extension on a script is being used to help
determine the context in which scripts should be run.

As a result, I think this feature should not be
accepted in this form, but warrants further thought to
make it easier to create a declarative way to specify
what the proper treatment of individual scripts should be.

I'm posting the patch so others can review it, and to
provide a record of these issues.