ActiveState using different MS runtime files than official Python release? (was Re: Movable Python or ActivePython)

[python at bdurham.com]

Hi Trent,

> That is probably a bug in the ZIP package (the MSI is by far the primary package for Windows so gets more attention).
> 
> I've started a bug for this:
> http://bugs.activestate.com/show_bug.cgi?id=86794

Thank you,

Malcolm


----- Original message -----
From: "Trent Mick" <trentm at activestate.com>
To: python at bdurham.com
Cc: python-list at python.org
Date: Thu, 06 May 2010 09:33:05 -0700
Subject: Re: ActiveState using different MS runtime files than official
Python release? (was Re: Movable Python or ActivePython)

On 10-05-05 5:30 PM, python at bdurham.com wrote:
> Hi Trent,
>
> On 10-05-05 12:04 PM, python at bdurham.com wrote:
>>> I just took a look at the ActiveStatre 2.6.5.12 release (zip file
>>> version) and noticed that this file does not include the MSVCR90.DLL run
>>> time file - it includes MFC*.DLL files instead (and a different manifest
>>> file as well).
>>>
>>> Can anyone explain why the ActiveState release uses different MS Visual
>>> C runtime files than the official Python Foundation's release of Python?
>
>> It doesn't. We use the same MSVC version as the python.org builds.
>>
>> Note that "MFC*.dll" files (IIRC, it has been a while) are
>> redistributable DLLs used by the included PyWin32 extensions that have
>> Python bindings for the Microsoft Foundation Classes GUI APIs.
>
> Yes, you are correct about the MFC*.dll's being shipped as part of the
> Py2Win32 extensions.
>
> But I don't see the MSVCR90.DLL in your ZIP release. I do see a
> MSVCR71.DLL.

That is probably a bug in the ZIP package (the MSI is by far the primary 
package for Windows so gets more attention).

I've started a bug for this:
http://bugs.activestate.com/show_bug.cgi?id=86794

Thanks,
Trent

-- 
Trent Mick
trentm at activestate.com
http://trentm.com/blog/