Finally, I managed to solve it!
The error was not a broken Python, but an incomplete wxPython installation!
Python had well been accessed, as long as I didn't mess around with PYTHONPATH;
it just couldn't find the wx stuff.
Thanks anyway for the time you took looking on my problem!
Best regards,
Tobias Conradt wrote:
> Having set PYTHONHOME=/home/conradt/usr/local makes no difference,
> any other setting now produces an *altered error message*:
>
> ImportError: No module named site
>
> Any clues?
Still a broken Python installation. The "site" module is part of the
standard library.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, I made a completely new installation of Python (2.7) in
my local path, re-built and -installed NumPy, wxWidgets and wxPython.
Then I re-configured, -built and -installed GRASS.
Requesting g.gui wxpython still leads to:
ERROR: wxGUI requires w
Dear Glynn, thanks for the quick reply!
The Python I use is system-wide installed in /usr/bin.
I've tried it with PYTHONHOME=/usr/lib64/python2.6 and
PYTHONHOME=/usr/lib64 to show the way to the standard
libraries, and I've tried PYTHONHOME=/usr/bin to tell
Python where to find itself. The result
Tobias Conradt wrote:
> I've successfully compiled and installed GRASS 6.4.0 svn
> (status of 7th July 2010). While the tcltk GUI runs fine,
> any attempt to start the wxpython GUI produces one of the
> following error messages:
>
> either:
>
> ERROR: wxGUI requires wxPython. No module named
Dear GRASS people,
I've successfully compiled and installed GRASS 6.4.0 svn
(status of 7th July 2010). While the tcltk GUI runs fine,
any attempt to start the wxpython GUI produces one of the
following error messages:
either:
ERROR: wxGUI requires wxPython. No module named wxversion
or (after
