[GRASS-dev] [GRASS GIS] #2873: Simplify usage of GRASS in Python from outside

GRASS GIS trac at osgeo.org
Sat Jan 23 14:58:21 PST 2016


#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 wenzeslaus):

 Replying to [comment:1 hellik]:
 > Replying to [ticket:2873 wenzeslaus]:
 > > GRASS Python packages could go to the system packages directory, so
 that we avoid the need for setting `PYTHONPATH`. This might work well on
 MS Windows when usage of system Python is implemented as described in
 #2333.
 >
 > there is no ''system Python'' in windows. users always has to install
 python manually systemwide, possibly interfering with other python
 installations installed by other software.

 By system Python I mostly mean what #2333 is talking about. Possible
 interference is the inherent issue of Windows operating system. I'm OK
 with including multiple options in the installer giving the choice to the
 user (with the last option being "Don't know what to choose? Install
 Ubuntu and let the package managers solve it for you." ;-).

 > > On MS Windows, putting more things on `PATH` is standard procedure
 from what I have seen...
 > > GRASS GIS executable should be on path on all platforms in the same
 way as it is on path in Linux. This is maybe not standard on MS Windows
 but at the end this is what users want (they want GRASS to be available
 right away).
 >
 > IMHO it is not a good practice to put ''everything'' in ''%PATH%'' in
 windows. ''poisoning'' %PATH% should be avoided IMHO.

 I'm not sure if we can do it. Is there a another way how to set path to
 dynamic libraries for a process (so that Python scripts using GRASS ctypes
 work)?

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



More information about the grass-dev mailing list