On Thu 22 Jun 2006 (15:44 +0200), Christian Anthon wrote: > Not easy to diagnose without more info (system and setup). Does the > users python setup work when run from the shell, that is running > python without arguments and entering import os.path should produce > something like > > [EMAIL PROTECTED] ~ $ python > Python 2.4.3 (#2, Apr 27 2006, 14:43:58) > [GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>import os.path > >>> > > > (ctrl + d to exit) > > Christian.
The other thing to do is to run gnubg from a command shell (on Unix/Linux, simply running gnubg from the command line, on Windows, I think you can run Command.com to get a DOS window and start gnubg from there) Then, in the terminal window type three greater than symbols to start python from within gnubg. in that window, type: print sys.path You should get a list of all the locations python will look for imports when started from within gnubg. If the directory where os.path.py is located appears, type import os.path let us know if that produces an error or simply gives another >>> prompt. -- Jim Segrave [EMAIL PROTECTED] _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
