Sounds like the Macports python is loading the system python global
site-packages (/Library/Python). Bad form really, because you can't expect
modules to work between different builds of python, even if they're the same
version. Maybe there is some option in Macports python to exclude the syst
Please add the outcome (solution) to this Wiki page:
http://grasswiki.osgeo.org/wiki/MacOSX_GRASS_errors
thanks
Markus
On Fri, May 23, 2014 at 10:22 AM, John Payne wrote:
> I set the path in .bash_profile set as you suggested ("export
> GRASS_PYTHON=/usr/bin/pythonw2.7"), and that did the tric
I can definitely say yes to all except PG. If I have a chance, I'll try to
install William's PGIS over the next few weeks and let you know.
Michael Barton
On May 23, 2014, at 10:22 AM, John Payne wrote:
> I set the path in .bash_profile set as you suggested ("export
> GRASS_PYTHON=/usr/bin
GRASS needs to be compiled with Postgres support to be able to store attribute
data in Postgres. Last I checked it doesn't handle Postgis directly, it's an
import and uses GDAL, so it doesn't need Postgres support for that.
On May 23, 2014, at 4:17 AM, Michael Barton wrote:
> I can definitely
Just FYI
On Fri, May 23, 2014 at 5:35 PM, William Kyngesburye
wrote:
> GRASS needs to be compiled with Postgres support to be able to store
> attribute data in Postgres. Last I checked it doesn't handle Postgis
> directly, it's an import and uses GDAL, so it doesn't need Postgres support
> fo
