Howard Lightstone wrote:
> On Tue, Apr 20, 2010 at 10:14 AM, Bill Janssen wrote:
>
> > Howard Lightstone wrote:
> >
> > > I've had a private Python25 install running with win32 for a while. I
> > > believe the trick is that the pythoncom25.dll and pywintypes25.dll have
> > to
> > > be in the
On Tue, Apr 20, 2010 at 10:14 AM, Bill Janssen wrote:
> Howard Lightstone wrote:
>
> > I've had a private Python25 install running with win32 for a while. I
> > believe the trick is that the pythoncom25.dll and pywintypes25.dll have
> to
> > be in the SAME folder as the python.exe that you want
Howard Lightstone wrote:
> I've had a private Python25 install running with win32 for a while. I
> believe the trick is that the pythoncom25.dll and pywintypes25.dll have to
> be in the SAME folder as the python.exe that you want to use (due to Windoze
> own variety of internal search paths for
I've had a private Python25 install running with win32 for a while. I
believe the trick is that the pythoncom25.dll and pywintypes25.dll have to
be in the SAME folder as the python.exe that you want to use (due to Windoze
own variety of internal search paths for DLLs). In my code, I also alter
th
Bill Janssen wrote:
> Mark Hammond wrote:
>
> > On 8/04/2010 12:05 PM, Bill Janssen wrote:
> > > I don't think I've tried that config. I'll give it a shot.
> > >
> > > [After trying it...] Nope, that may be necessary, but it's not
> > > sufficient. I installed Python in a private directory "
