Where is wxPython?

[Joel Lucsy]

Another idea we use quite a bit in my office is to use delay loading, then
load the dll specifically with full path from where you expect it to be. Of
course this requires MSVC6, but it does work quite well.

--
Joel Lucsy (jjlucsy at concentric.net)

"Robin Dunn" <robin at alldunn.com> wrote in message
news:8t77t1$ndf$1 at nnrp1.deja.com...
> In article <Wa32OZ5KzxUMWNpWxW=iRT6XyPXv at 4ax.com>,
>   Paul Moore <paul.moore at uk.origin-it.com> wrote:
>
> >
> > Fiddling in the registry is even worse...
> >
>
> I agree.
>
>
> > Actually, I believe that you should be able to put the DLL in the same
> > directory as the DLL which uses it (ie, the wxPython PYD file). I've
> > done this with other modules and it seems to work.
> >
> > Basically, Python itself loads DLLs (PYDs) from explicit directories
> > in sys.path. If these DLLs load other DLLs, I believe that the search
> > path includes the directory in which the loading DLL is located,
> > rather than the directory in which the original EXE is located. The
> > Windows documentation seems to imply otherwise - all I can say is that
> > it seems to work.
>
> I'm sure I tried that before and it didn't work...  But it *is* working
> for me now with both 1.5.2 and 2.0.  Perhaps it is a win2k thing, which
> version of windows are you running?
>
> --
> Robin Dunn
> Software Craftsman
> robin at AllDunn.com
> http://wxPython.org     Java give you jitters?
> http://wxPROs.com        Relax with wxPython!
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>