Send grass-windows mailing list submissions to
        grass-windows@lists.osgeo.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.osgeo.org/mailman/listinfo/grass-windows
or, via email, send a message with subject or body 'help' to
        grass-windows-requ...@lists.osgeo.org

You can reach the person managing the list at
        grass-windows-ow...@lists.osgeo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-windows digest..."


Today's Topics:

   1. Re: Fwd: WinGRASS installation and addtional python       modules
      (Glynn Clements)
   2. Re: Fwd: WinGRASS installation and addtional python       modules
      (Johannes Radinger)


----------------------------------------------------------------------

Message: 1
Date: Wed, 18 May 2011 09:00:26 +0100
From: Glynn Clements <gl...@gclements.plus.com>
Subject: Re: [GRASS-windows] Fwd: WinGRASS installation and addtional
        python  modules
To: "Johannes Radinger" <jradin...@gmx.at>
Cc: grass-windows@lists.osgeo.org
Message-ID: <19923.31898.359330.920...@cerise.gclements.plus.com>
Content-Type: text/plain; charset=us-ascii


Johannes Radinger wrote:

> Okay so what I've done now is:
> 
> 1) Installed Python 2.7
> 2) Installed addtional Python modules (Numpy, Scipy, Matplotlib)
> 3) Installed WinGRASS 6.4.1 (recent package for Windows)
> 4) Created following environmental variables:
>    GRASS_PYTHON C:\Python27\python
>    PYTHONPATH  %GISBASE%\etc\python
> 5) Restarted Windows (don't know if needed)
> 
> Now two questions
> 1) Is everything done correctly

You appear to have missed a key step.

The WinGRASS package tries to bundle Python, which causes problems if
you want to write Python scripts for GRASS. You should remove both the
bundled Python and any references to it.

> and how can I check it (GRASS works,
> but how to check if grass can access the python modules (Scipy)?

> 2) Where do I have to store my python-script to call it from GRASS
> (bin folder in the lib in Mac OS)?

Place the script in %GISBASE%\bin. The script itself will work
regardless of its location, but the code which generates the wxPython
parameter dialogs requires the script to be in the path.

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


------------------------------

Message: 2
Date: Wed, 18 May 2011 11:08:36 +0200
From: "Johannes Radinger" <jradin...@gmx.at>
Subject: Re: [GRASS-windows] Fwd: WinGRASS installation and addtional
        python  modules
To: Glynn Clements <gl...@gclements.plus.com>
Cc: grass-windows@lists.osgeo.org
Message-ID: <20110518090836.34...@gmx.net>
Content-Type: text/plain; charset="utf-8"


-------- Original-Nachricht --------
> Datum: Wed, 18 May 2011 09:00:26 +0100
> Von: Glynn Clements <gl...@gclements.plus.com>
> An: "Johannes Radinger" <jradin...@gmx.at>
> CC: grass-windows@lists.osgeo.org
> Betreff: Re: [GRASS-windows] Fwd: WinGRASS installation and addtional python  
> modules

> 
> Johannes Radinger wrote:
> 
> > Okay so what I've done now is:
> > 
> > 1) Installed Python 2.7
> > 2) Installed addtional Python modules (Numpy, Scipy, Matplotlib)
> > 3) Installed WinGRASS 6.4.1 (recent package for Windows)
> > 4) Created following environmental variables:
> >    GRASS_PYTHON C:\Python27\python
> >    PYTHONPATH  %GISBASE%\etc\python
> > 5) Restarted Windows (don't know if needed)
> > 
> > Now two questions
> > 1) Is everything done correctly
> 
> You appear to have missed a key step.
> 
> The WinGRASS package tries to bundle Python, which causes problems if
> you want to write Python scripts for GRASS. You should remove both the
> bundled Python and any references to it.

So if I understand you correctly I can do as a 6th step the removing of the 
python2.5 which comes with winGRASS. What do you mean exactly with removing, 
deleting the python2.5 folder in programms/grass6.4.1/? 

Which references have to be removed? There were no environemental variables 
created during the winGRASS installation pointing to Python25 (the winGRASS 
python).

/johannes

> 
> > and how can I check it (GRASS works,
> > but how to check if grass can access the python modules (Scipy)?
> 
> > 2) Where do I have to store my python-script to call it from GRASS
> > (bin folder in the lib in Mac OS)?
> 
> Place the script in %GISBASE%\bin. The script itself will work
> regardless of its location, but the code which generates the wxPython
> parameter dialogs requires the script to be in the path.
> 
> -- 
> Glynn Clements <gl...@gclements.plus.com>

-- 
NEU: FreePhone - kostenlos mobil telefonieren und surfen!                       
Jetzt informieren: http://www.gmx.net/de/go/freephone


------------------------------

_______________________________________________
grass-windows mailing list
grass-windows@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-windows


End of grass-windows Digest, Vol 56, Issue 3
********************************************

Reply via email to