Changes between Version 46 and Version 47 of GSoC/2018


Ignore:
Timestamp:
Mar 11, 2018, 12:59:15 PM (6 years ago)
Author:
neteler
Comment:

link to ​https://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly#Python:_GRASS_GIS_7_with_an_external_library:_grass-session

Legend:

Unmodified
Added
Removed
Modified

  • GSoC/2018

    v46 v47  
    303303  * `GRASS_BATCH_JOB`: same as newer `--exec` but through environmental variable and more limited
    304304  * Use `grass.script.setup` package from GRASS GIS (requires boilerplate to add the packages on path first) 
    305   * Use the standalone `grass_session` package (new)
     305  * Use the standalone `grass_session` package (new, see [https://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly#Python:_GRASS_GIS_7_with_an_external_library:_grass-session here])
    306306  * Set up environmental variables and "RC file" yourself (the classic method).
    307307 * None of these allows the user to skip the database setup phase. This leads to the need for constant reimplementing of setup, import and export steps in various software and environments including ''user scripts'' (in Bash, Python, R), QGIS Processing, gvSIG/SEXTANTE, uDig/JGrassTools, and all the web/server/cloud tools and applications which use GRASS GIS as a processing backend (e.g. PyWPS server).