Where is wxPython?

[jay.krell at cornell.edu]

>> I am also sure that there is/was an issue there. Perhaps it
>> was only some of the special MS DLL's (MSVCRT.DLL et al)
>> that must  live in the system directory?

NT/Win2000: Part of the answer alluded to is that "knowndlls", at least if
referenced without an explicit path, are only ever loaded out of
%windir%\system32. The knowndlls are set in the registry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\KnownDLLs, plus their static dependents. Look under \KnownDlls with
www.sysinternals.com's winobj. Msvcrt.dll is there. The knowndlls are a
relatively small set, around 20, vastly shorter than the contents of
system32, over 600 .dlls on my NT4 system.

And again, an already loaded .dll will often precede loading what searching
would otherwise find.

Win9x/Me: I don't know.

 - Jay

-----Original Message-----
From: Robin Dunn <robin at alldunn.com>
Newsgroups: comp.lang.python
To: python-list at python.org <python-list at python.org>
Date: Thursday, October 26, 2000 9:57 PM
Subject: Re: Where is wxPython?


>In article <So1K5.359$VF3.501 at news.more.net>,
>  "Jeff Kunce" <kuncej at mail.conservation.state.mo.us> wrote:
>> > > > Actually, I believe that you should be able to put the DLL in
>the
>> > > > same directory as the DLL which uses it
>>
>> I am also sure that there is/was an issue there. Perhaps it
>> was only some of the special MS DLL's (MSVCRT.DLL et al)
>> that must  live in the system directory?
>>
>> It might be a good idea to check with a windows guru
>> (Mark Hammond?) to figure out what the DLL path issue
>> is all about.
>>
>
>Well, I'm about to have a trial by fire over this issue as I just
>released a new set of installers that put the wxWindows DLL in the
>wxPython package directory...
>
>
>--
>Robin Dunn