#932: Wingrass7 - ImportError: No module named grass - Fix PYTHONPATH?
---------------------+------------------------------------------------------
Reporter: hellik | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: default | Version: svn-trunk
Keywords: | Platform: MSWindows Vista
Cpu: x86-32 |
---------------------+------------------------------------------------------
self compild grass7 in the osgeo4w-stack
if i want to start for example
''v.db.addcolumn'' from the wx-table-manager, there is following error:
{{{
Traceback (most recent call last):
File "C:\osgeo4w\usr\src\grass_trunk\dist.i686-pc-
mingw32\v.db.addcolumn.py", line 52, in <module> import grass.script as
grass
ImportError: No module named grass.script
}}}
#932: Wingrass7 - ImportError: No module named grass - Fix PYTHONPATH?
------------------------------+---------------------------------------------
Reporter: hellik | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: default | Version: svn-trunk
Resolution: | Keywords:
Platform: MSWindows Vista | Cpu: x86-32
------------------------------+---------------------------------------------
Comment (by glynn):
Replying to [ticket:932 hellik]:
> so where should this change integrated directly in source for working
wingrass7 out of the box?
set_paths in lib/init/functions.sh already sets PYTHONPATH, provided that
it isn't already set.
Python itself is going to expect PYTHONPATH to be in native Windows
format. However, MSys may "fix" environment variables when invoking non-
MSys programs.
If this is an OSGeo4W-specific issue, it should be dealt with as such.
Nothing in the GRASS source tree should be hard-coding OSGeo4W-specific
settings.