[GRASS-user] GRASS, ArcGIS, and Python incompatibilties

Yes. That’s great it is working for you. But in our case, it won’t launch the wxPython GUI and generates a Python error that it cannot find the correct version of Python. This is the stock version of GRASS that works for you and others (so Python is OK there) and Python works fine in ArcGIS, so it is OK there. So the signs point strongly to some kind of path/python path issue.

Michael

On Jun 30, 2012, at 1:00 PM, <grass-user-request@lists.osgeo.org>
wrote:

From: gene <martin.laloux@gmail.com>

Subject: Re: [GRASS-user] GRASS, ArcGIS, and Python incompatibilties

Date: June 29, 2012 3:40:28 PM MDT

To: <grass-user@lists.osgeo.org>

Glynn Clements wrote

remove it’s bundled Python, unset any PYTHONHOME or PYTHONPATH variables,

etc).

I repeat, I think this is not the problem. We are running QGIS 1.7.4, 1.8,
GRASS GIS 6.2.4 and 7 dev, ArcGIS 10 and standard Python 2.5 without problem
(Windows XP)

Each version of Python (2.5,2.6 and 2.7) works independently without problem
.


View this message in context: http://osgeo-org.1560.n6.nabble.com/GRASS-ArcGIS-and-Python-incompatibilties-tp4984692p4984993.html
Sent from the Grass - Users mailing list archive at Nabble.com.


C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

What versions of Python are in the registry database ?
What is the error message ? (detail of the version mismatch)

You can compare the paths used by the Python versions in ArcGIS (from the
Python console) and in GRASS GIS (from the msys shell)

import sys
print sys.path

Normally the result should be different. If they are some same elements,
look if there are PYTHONHOME or PYTHONPATH variables defined in the PATH
variable or in the registry database as Glynn Clements wrote. How Windows
defines these variables is a bit complex...

--
View this message in context: http://osgeo-org.1560.n6.nabble.com/GRASS-ArcGIS-and-Python-incompatibilties-tp4984692p4985096.html
Sent from the Grass - Users mailing list archive at Nabble.com.