![]() ![]() |
||
![]() |
![]() |
|
![]() |
[wingide-users] Error messages at winglite launchStephen Boulet stephen@theboulets.netSat, 18 May 2002 13:37:07 -0500
Hmm. Still the same error when setting PYTHONPATH in the project properties. I think that the following is the problem. I execute this as a regular user: $ /usr/bin/env python 'import site' failed; use -v for traceback Python 2.2.1 (#1, May 4 2002, 06:49:16) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] on linux2 Type "help", "copyright", "credits" or "license" for more information. But as root: root]# env python Python 2.2.1 (#1, May 4 2002, 06:49:16) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] on linux2 Type "help", "copyright", "credits" or "license" for more information. I know this really isn't wingide's fault, but any help appreciated all the same! ;) -- Stephen On Saturday 18 May 2002 07:47 am, you wrote: > On Fri, 17 May 2002, Stephen Boulet wrote: > > $ export PYTHONPATH=/usr/lib/python2.2 > > $ export PYTHONHOME=/usr/lib/python2.2python > > $ winglite > > /usr/local/bin/winglite: gtk-config: command not found > > 'import site' failed; use -v for traceback > > Traceback (most recent call last): > > File "<string>", line 1, in ? > > ImportError: No module named os > > > > I'm using linux with Mandrake 8.2. > > > > Thanks for any help! > > Looks like setting PYTHONHOME is confusing Wing so that it fails to find > the Python interpreter to use for your debug process. > > You shouldn't need to set this. Instead, specify the python to use > with your debug process from the Project Properties / Python Executable > area. > > You can actually also set PYTHONPATH in the Environment area with > radio button Add to Env checked. But apparently setting PYTHONHOME > there is also problematic. This is a bug that needs to be fixed. > > Thanks for reporting this. > > - Stephan
Run by Mailman v 2.0.8 |
|
|
Copyright (c) 2000-2002, Archaeopteryx Software, Inc. Legal Statements | ||