Thomas Heller wrote:
It would be for 2.5, anyway, and I have hoped that bdist_wininst would
be replaced by bdist_msi then ;-). What are your plans for that?
I still hope to write one by for 2.5.
One issue is that you cannot have multiple installations of an MSI
package. So if you want to support d
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Thomas Heller wrote:
>>>This means that if you build a windows installer using
>>>distutils - it *requires* msvcr7.dll in order to run. This is true even
>>>if your package is a pure python package. This means that when someone
>>>tries to use a wind
Thomas Heller wrote:
> [CC to python-dev]
> "Fuzzyman" <[EMAIL PROTECTED]> writes:
>
> > Python 2.4 is built with Microsoft Visiual C++ 7. This means that
it
> > uses msvcr7.dll, which *isn't* a standard part of the windows
operating
> > system.
>
> Nitpicking - it's MSVC 7.1, aka MS Visual Studio
Thomas Heller wrote:
This means that if you build a windows installer using
distutils - it *requires* msvcr7.dll in order to run. This is true even
if your package is a pure python package. This means that when someone
tries to use a windows installer created with Python 2.4, on a machine
with only
[CC to python-dev]
"Fuzzyman" <[EMAIL PROTECTED]> writes:
> Python 2.4 is built with Microsoft Visiual C++ 7. This means that it
> uses msvcr7.dll, which *isn't* a standard part of the windows operating
> system.
Nitpicking - it's MSVC 7.1, aka MS Visual Studio .NET 2003, and it's
msvcr71.dll.
>
