Re: [python-win32] sys.path and PyWin32 scripting engine

2010-07-20 Thread Mark Hammond
On 21/07/2010 2:45 AM, Tim Roberts wrote: Marc-Andre Belzile wrote: I'm referring to Python Active Scripting engines available in pywin32. I'm creating them through COM, so I don't tknow if the ActiveX goes through Py_NewInterpreter or not. Active Scripting creates Python as an out-of-proc

Re: [python-win32] sys.path and PyWin32 scripting engine

2010-07-20 Thread Tim Roberts
Marc-Andre Belzile wrote: > I'm referring to Python Active Scripting engines available in pywin32. I'm > creating them through COM, so I don't tknow if the ActiveX goes through > Py_NewInterpreter or not. Active Scripting creates Python as an out-of-process COM server. That means there will be

Re: [python-win32] sys.path and PyWin32 scripting engine

2010-07-20 Thread Marc-Andre Belzile
[mailto:python-win32-bounces+marc-andre.belzile=autodesk@python.org] On Behalf Of Tim Roberts Sent: Monday, July 19, 2010 3:37 PM To: python-win32@python.org Subject: Re: [python-win32] sys.path and PyWin32 scripting engine Marc-Andre Belzile wrote: > > > > Is the value of sy

Re: [python-win32] sys.path and PyWin32 scripting engine

2010-07-19 Thread Tim Roberts
Marc-Andre Belzile wrote: > > > > Is the value of sys.path private for each new scripting engine I > create ? Or is it global value ? > > > > According to my test results, any new paths added to sys.path from a > specific engine seems to be available to others. Is it the expected > behavior ?