Bryan Feir wrote: > On Thu, Aug 23, 2007 at 10:41:16AM +1000, John Pye wrote: > >> Conclusion: whereever the code is that checks for the existance of >> msvcr71.dll, it should also search in the Python installation directory, >> in addition to the PATH. Try Dependency Walker for the steps that are >> followed when Windows hunts for a DLLs. >> >> Question: *sometimes* msvcr71.dll is available in the Windows directory. >> What installs it? Is it reasonable to assume that any up-to-date Windows >> system will always have a copy of this DLL? If I had simply performed by >> Windows Update thing, perhaps I wouldn't have seen this problem. >> > > What installs it is the Visual Studio development environment. > MSVCR71 is the MicroSoft Visual C Runtime 7.1, which comes with Visual C > 7.1, which is part of Visual Studio .NET 2003. You can tell which > version of Visual Studio was used by the numbers: programs compiled > under Visual Studio 2005 link to msvcr8.dll instead, for example. >
I haven't got any of those MSVS things on my system, so it can't be that. You're sure that msvcr71.dll isn't installed by Windows Update? > And no, said DLLs are not generally included with Windows by default. > They are, however, free to include in the archives of programs that > require them, which is what happens with Python. > Cheers JP _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
