Python(path) and the location of the Python DLL.
stephen at cerebralmaelstrom.com
Mon May 15 15:03:05 EDT 2000
My second question was just where to change that -- to have my dll check in
a different place in the registry for the .py/etc files. :)
And I never said anything about shipping. 1.6 will no doubt be done by the
time that i'm done with this, and i'll just be upgrading what i'm using
throughout the development. Heck, this may never get done. Its a personal
project to fill a software gap which has been irritating me for years. :)
Warren Postma <embed at geocities.com> wrote in message
news:wnUT4.20382$HG1.516944 at nnrp1.uunet.ca...
> "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
> > 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
> 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
> 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