Python(path) and the location of the Python DLL.
embed at geocities.com
Mon May 15 17:02:05 CEST 2000
"Stephen" <stephen at cerebralmaelstrom.com> wrote in message
news:XwOT4.8283$WS3.66942 at typhoon.we.rr.com...
> Hello, all.
> I'm working on embedding Python into a program i'm working on in
> I got past the problem of importing VC++ DLLs into C++Builder by searching
> Dejanews, so now before I continue I have a couple questions...
> #1) I'll be using the latest version (1.6a2), but I don't want it to get
> involved with any current versions running on the same machine. Is there
> anything wrong with me renaming the DLL?
This sounds scary. The Windows python implementation checks the Registry to
find the python path. If you have two dlls, they'll have PYD files and PY
files in the same directory, or else you'll have to build your own version
of the python dll, that checks somewhere else in the registry for it's path
and so on. Why not just have your installation program check for
incompatible DLLs and warn the user when Python is already installed and
it's a different version. One of the two versions is newer or better.
Plus, I wonder, why are you making plans to ship alpha software as a
production release? Silly.
More information about the Python-list