On 3/3/2011 2:32 PM, Sridhar Ratnakumar wrote:
>
> That's an old bug, and I believe the fix is simple (see comment #2). Are
> you still looking for a fix in 2.5? Or 2.7?
For our purposes, a fix for 2.7 would be sufficient. Can't speak to
others' needs.
--
Bob Kline
http://www.rksystems.com
mai
Hi Bob,
Trent is no longer at ActiveState.
That's an old bug, and I believe the fix is simple (see comment #2). Are you
still looking for a fix in 2.5? Or 2.7?
-srid
On 2011-03-03, at 6:08 AM, Bob Kline wrote:
> Hi, Trent. How's progress on this bug?
>
> http://bugs.activestate.com/show_bug
Hi, Trent. How's progress on this bug?
http://bugs.activestate.com/show_bug.cgi?id=72603
--
Bob Kline
http://www.rksystems.com
mailto:bkl...@rksystems.com
___
ActivePython mailing list
ActivePython@listserv.ActiveState.com
To unsubscribe: http://lists
>> 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
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
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
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.
