Ask Your Question

Revision history [back]

Assuming it works outside of Wing, then the problem is that Wing is not using the right env.  One simple solution is to start Wing from the command line environment in which the imports do work.  That may help if Wing picks up the right Python to use.Or try comparing the following inside Wing and outside:import sys, ossys.executablesys.pathos.environ['LD_LIBRARY_PATH']These can be set/modified using Python Executable, Python Path, and Environment in Wing's Project Properties.On Linux it may also be that you have say 32-bit libSDL and Python is running 64-bit, though this seems less likely.

click to hide/show revision 2
No.2 Revision

Assuming it works outside of Wing, then the problem is that Wing is not using the right env.  One simple solution is to start Wing from the command line environment in which the imports do work.  That may help if Wing picks up the right Python to use.Or use.

Or try comparing the following inside Wing and outside:import outside:

import sys, ossys.executablesys.pathos.environ['LD_LIBRARY_PATH']These os
sys.executable
sys.path
os.environ['LD_LIBRARY_PATH']

These can be set/modified using Python Executable, Python Path, and Environment in Wing's Project Properties.On Properties.

On Linux it may also be that you have say 32-bit libSDL and Python is running 64-bit, though this seems less likely.