We're building a new production server for one of our systems, and
thought it would be a good time to bump up that system from Python 2.4
to 2.5. Problem is, the web server, running under the machine's system
account, can't see the registered COM libraries we've hooked in with the
MakePy tool.
Trent Mick wrote:
>> 1. Why the change?
>>
>
> This was a change in core PyWin32. I don't want to put words in the
> mouths of the PyWin32 developers, but I suspect the change was to (a)
> avoid putting temp info in the install area
Hmm. I'm all for having them avoid dropping temporary dr
>> I'd also ask on [EMAIL PROTECTED] to verify the reasoning for
>> the change. Now that I think about it, the change could also be that
>> ActivePython's installer just now doesn't create that dir. It is
>> possible that that was an unintended subtle change.
>>
>
> Seems like the most like
Bob Kline wrote:
> We're building a new production server for one of our systems, and
> thought it would be a good time to bump up that system from Python 2.4
> to 2.5. Problem is, the web server, running under the machine's system
> account, can't see the registered COM libraries we've hooked
