#2873: Simplify usage of GRASS in Python from outside
-------------------------+-------------------------------------------------
Reporter: wenzeslaus | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: major | Milestone: 7.1.0
Component: Python | Version: svn-trunk
Resolution: | Keywords: startup, installation, scripts,
| interpreter, windows installer, pygrass,
CPU: | temporal, bootstrap, boilerplate
Unspecified | Platform: All
-------------------------+-------------------------------------------------
Comment (by glynn):
Replying to [ticket:2873 wenzeslaus]:
> The `GRASS_EXECUTABLE` does not have to be set if `grass` is on the path
or, in theory, if it is in on some standard path
IMHO, this "solution" is yet more duct tape on top of the existing heap.
Any real solution would start by simply deleting the GRASS startup script
then figuring out what needs to be done to make everything still work
without it.
It should not be necessary to "start" GRASS.
On Unix, GRASS modules and libraries should be installed in system
directories. Python packages should go in Python's site-packages
directory. Environment variables should be set in /etc/profile (or
whatever mechanism the distribution uses, e.g. /etc/profile.d).
On Windows, configuration settings should probably be stored in the
registry.
GISRC should have a system-wide default setting such as $(HOME)/.grass/rc.
Users who never need more than one session at a time can just use that
file always, changing the database, location or mapset with g.mapset.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2873#comment:6>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
