[GRASS-dev] Re: python not launching in trunk

Martin,

I am only receiving this error with wxGUI, not with any other wxPython applications. It also only happens AFTER the initial gis_setup.py screen (i.e., in wxPython and working fine) when it tries to start wx_gui.py.

Given my other problem mentioned earlier, I'm concerned that this is the result of an internal version check that is failing on the Mac even if correct version are installed.

Glynn may be right about a PYTHONPATH problem, but I do have an extensive, and AFAICT correct, PYTHONPATH on that computer. I may try to update GRASS and compile on my MacBook this weekend to see if it is something specific to my office computer or if it is something that changed in the GRASS source code.

Something interesting that William Kyngesbury just said that helps one issue I'm having. Apparently the startup app for GRASS compiled on a Mac ignores the .grass_bashrc file. This is not where my PYTHONPATH is located, but is where I was putting some environmental settings related to a Python issue on the MacBook--and they were not taking.

Michael
____________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

On Jul 26, 2008, at 1:48 AM, Martin Landa wrote:

Michael,

2008/7/25 Michael Barton <michael.barton@asu.edu>:

I just checked out a brand new copy of GRASS 7 from trunk and compiled. When
I went to start, I got...

Fatal Python error: Interpreter not initialized (version mismatch?)

I've got Python 2.5.2 and wxPython 2.8.7 installed correctly. Any idea what
is wrong?

I slightly remember you had similar problem in the past. There's
something broken on your computer. After some googling

Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos

"""Q. "Fatal Python error: Interpreter not initialized (version mismatch?)"

A. This error occurs when the version of the Python interpreter for
which the extension module has been built is different from the
version of the interpreter that attempts to import the module.

The header file python.h contains a #pragma directive that
automatically links your DLL with the import libary for the Python
interpreter DLL. If you have installed Python version 2.3, the LIB
file is python23.lib and the required DLL is python23.dll.

When the interpreter that performs the import is, say, version 2.2,
you receive this error. You also receive the error when you attempt to
import a Debug version of the extension DLL into a Release build of
the interpreter."""

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Michael Barton wrote:

I am only receiving this error with wxGUI, not with any other wxPython
applications. It also only happens AFTER the initial gis_setup.py
screen (i.e., in wxPython and working fine) when it tries to start
wx_gui.py.

Given my other problem mentioned earlier, I'm concerned that this is
the result of an internal version check that is failing on the Mac
even if correct version are installed.

Glynn may be right about a PYTHONPATH problem, but I do have an
extensive, and AFAICT correct, PYTHONPATH on that computer. I may try
to update GRASS and compile on my MacBook this weekend to see if it is
something specific to my office computer or if it is something that
changed in the GRASS source code.

Something interesting that William Kyngesbury just said that helps one
issue I'm having. Apparently the startup app for GRASS compiled on a
Mac ignores the .grass_bashrc file. This is not where my PYTHONPATH
is located, but is where I was putting some environmental settings
related to a Python issue on the MacBook--and they were not taking.

The contents of ~/.grass.bashrc are copied into the <mapset>/.bashrc
file, which is loaded by the session shell. It doesn't affect anything
other than the session shell (e.g. Init.sh, or any GUI spawned from
it).

Also, note that some Python scripts are run using $GRASS_PYTHON, while
others use "python". If $GRASS_PYTHON is something other than
"python", you will get varying behaviour.

Specifically, Init.sh uses $GRASS_PYTHON to run gis_set.py but,
AFAICT, nothing else uses that variable. The wxgui script (which is a
shell script) uses "python", as does g.gui. Any scripts which are run
directly will use the #! line, which will presumably use "python" (you
can't use environment variables there, and I don't know if the Tcl
"polyglot hack" has a Python equivalent).

--
Glynn Clements <glynn@gclements.plus.com>