Re: Python, Windows, OpenSSL and applink.c (was Execute connect_ssl() twice...)

>
> >
> > It sure would be nice to be able to distribute Python/OpenSSL apps
> > without having to ask every casual Windows user to recompile Python.
> > Does it make sense the distribution versions of python.exe be pre-
> > built with applink?  ...conditional to windows only.  Yes?  No?  Does
> > compiling in applink cause problems elsewhere?
> >
>

I think it strange to have this conditional to Windows, but then again
Windows tries to show that it is special wherever it can including making a
pest of itself... Maybe the question is: which is better - to include
applink in all apps regardless of platform as a "fix" to the runtime issues
in Windows or to remove the dependency in Windows and allow applications on
different platforms to work the same? In other words, if applink is built
into python (and any other app), the aforementioned problem goes away, but
in effect applink becomes a sort of IO standard that must be included
whenever building Windows apps using python. Is this desirable?

I was able to make everything work without patching in applink as long as I
built everything with the same compiler and removed the calls from openssl,
but with the side effects described in the previous thread. So this time the
question is, do we limit ourselves on what compiler to use?

Which is the worst evil? To use the same compiler for everything or to use
the same file in different apps? In my case, I'll use the same compiler. I
like things to be consistent regardless of the platform. It makes it easier
to debug. Of course, situations change, and I may think differently in a
different situation...