Problem Python 2.6.1 vs 2.6 & pyWin32

[Mark Hammond]

On 25/03/2009 11:06 AM, John Machin wrote:
> It would appear that the safest cover-most-bases option for a developer/packager
> of pure-Python packages (especially one intended to be runnable on older
> versions of Python, some as far back as 2.1) is to use Python 2.5 to make the
> bdist_wininst (the exe is linked against msvcr71.dll which is widely available
> and doesn't have SxS problems).

Hi John,

   Note that fairly recently (IIRC, 2.6.2/3.1), the bdist_wininst stub 
installers moved to linking the CRT statically, so should avoid this 
problem.  Indeed, if you use the correct magic, you should be able to 
use this version of distutils to build binaries for much earlier 
versions of Python and to allow the installer itself for that version to 
avoid depending on any msvcrt...

Cheers,

Mark