[wingide-users] Different sys.path between Python Shell and Debug Probe

Jonathan Mozes jon at rayv.com
Wed Feb 13 01:22:51 MST 2008


sys.path is the same (except the debug\\tserver) between the Python
Shell Tool and an external Python Shell.
However, I don't have a PYTHONSTARTUP variable setup, so that probably
isn't the cause for the difference.

Jon

-----Original Message-----
From: Wingware Support [mailto:support at wingware.com] 
Sent: Tuesday, February 12, 2008 19:45
To: Jonathan Mozes
Cc: wingide-users at wingware.com
Subject: Re: [wingide-users] Different sys.path between Python Shell and
Debug Probe

Jonathan Mozes wrote:
> An interesting difference between the Python Shell Tool and the Debug 
> Probe Tool is that their sys.path list is different.
> 
> This, of course, causes module execution to differ between the two 
> tools. Any idea why this is happening?

I suspect you have PYTHONSTARTUP defined and that's being loaded
in the Python Shell but not in the debug process, which then
defines the state in the Debug Probe.

Do you see the same sort of differences (other than inclusion of
our debug\\tserver of course) when you compare the Python shell
outside of Wing and running your code outside of Wing?

The environment can also be affected by which file you're debugging
if you've set up per-file debug properties in your project.  But
this seems less likely, from what you wrote and looking at the
significantly different environment.

Please let me know if that doesn't explain it...

-- 

Stephan Deibel
Wingware | Python IDE
Advancing Software Development

www.wingware.com



More information about the wingide-users mailing list