Can somebody kill getpathp for me?

[Chris Gonnerman]

----- Original Message -----
From: "Mark Hammond" <mhammond at skippinet.com.au>


> Tim Peters wrote:
> > [Chris Gonnerman]
>
> >>What I want is a version of either python.exe or python21.dll
> >>(whichever contains the offending getpathp.c module) with the
> >>registry-probing code disabled.
> >>
> >
> > If that's what you really want, you'll have to edit getpathp.c and
compile
> > your own Python.
>
> Or, use MSVC or some other resource editor to change the single string
> resource in the compiled Pythonxx.DLL (ie, no need to rebuild the DLL).
>   This will cause a different registry key to be used (by the core, and
> also by extensions that are registry aware).

If I had MSVC I'd build from source.  I work in a mixed Linux/Windows
environment, and use Python for just about everything.  My days as
a C programmer are probably mostly in the past.

Wonder if I can find some other resource editing tool... time to STFW.