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 dross in the 
install area, but surely the generated COM modules themselves aren't 
temporary.

>  ... and (b) it would seem to allow per-user COM registration.
>    

Well, allowing per-user COM registration would seem to be significantly 
different from silently changing to per-user COM registration.
>    
> >  2. What do we need to do to make the generated modules available to any 
> > account on the system?
> >     
> 
>  Poking aroiund in the sources, the directory where these generated files 
>  get places in win32com.__gen_path__. That is determined (via quite a bit 
>  of code) in win32com/__init__.py.
> 
>  It *looks* (tho I'm just eyeballing the code), that you can control it 
>  with a registry setting (tho perhaps that's mainly for debugging/dev). 
>  Also it appears that if .../Lib/site-packages/win32com/gen_py exists, 
>  then that will be used.
> 
>  ...tries it...
> 
>  Yup. Try creating that dir.
>    

Yes, that works.

> 
>  I'd also ask on python-win32@[...].org 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 likely explanation.  Perhaps you might want to have 
the installer modified to revert back to the original behavior.

-- 
Bob Kline
http://www.rksystems.com
mailto:bkline@[...].com

_______________________________________________
ActivePython mailing list
ActivePython@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/ActivePython