[GRASS-dev] [GRASS GIS] #3057: Problems with Numpy and matplotlib after updating through OSGeo4W

GRASS GIS trac at osgeo.org
Fri Nov 11 06:42:26 PST 2016


#3057: Problems with Numpy and matplotlib after updating through OSGeo4W
--------------------------+---------------------------------
  Reporter:  veroandreo   |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  critical     |  Milestone:  7.0.6
 Component:  Python       |    Version:  svn-releasebranch72
Resolution:               |   Keywords:  wingrass
       CPU:  Unspecified  |   Platform:  MSWindows 7
--------------------------+---------------------------------

Comment (by hellik):

 Replying to [comment:18 hellik]:
 >
 > I'm getting closer now to the issue:
 >
 >
 > next steps:
 >
 > - copy env.bat and grass72svn.bat from the ''C:\Program Files\GRASS GIS
 7.2.svn\'' installation to a folder, e.g. D:\temp\testgrasspython
 >
 > - in D:\temp\testgrasspython\grass72svn.bat, ''set GISBASE=C:\Program
 Files\GRASS GIS 7.2.svn'' points to the standalone installation
 >
 > - change in D:\temp\testgrasspython\env.bat that the python stuff points
 to the OSGeo4W-python:
 >
 > {{{
 > set GRASS_PYTHON=C:\OSGeo4W64\bin\python.exe
 > set PYTHONHOME=C:\OSGeo4W64\apps\Python27
 > }}}
 >
 > and now you get in the standalone installation (while pointing to the
 OSGeo4W-python stuff) the same numpy error in startup like in the OSGeo4W-
 winGRASS.

 now tested it the other way around:

 taking the OSGeo4W-winGRASS-installation; regarding python let's point to
 the python stuff living in ''C:\Program Files\GRASS GIS 7.3.svn'' and
 start OSGeo4W-winGRASS-7.3.svn

 => with pointing to the standalone installer python, also OSGeo4W-
 winGRASS-7.3.svn starts '''without''' any numpy problem nor any problem
 with raster profiling, bivariate scatterplots etc.

 >
 > conclusion:
 >
 > there must be a difference between the ''python stuff of the standalone-
 winGRASS-build environment'' and the ''OSGeo4W-provided python stuff''!!
 >

 yes confirmed, there is definitely some issue with OSgeo4W's python stuff.
 tested on 3 different winboxes (7,8,10) with a fresh OSGeo4W installation.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3057#comment:22>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list