Timeline for Capturing Output Messages from GRASS when Running Python Scripts
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 15, 2017 at 7:51 | history | edited | PolyGeo♦ |
edited tags
|
|
| Aug 24, 2016 at 18:50 | history | edited | PolyGeo♦ | CC BY-SA 3.0 |
deleted 18 characters in body
|
| S Jan 24, 2016 at 1:11 | history | suggested | wittich |
add grass-70 tags
|
|
| Jan 23, 2016 at 22:00 | review | Suggested edits | |||
| S Jan 24, 2016 at 1:11 | |||||
| Jan 19, 2016 at 14:54 | vote | accept | fdonnelly | ||
| Jan 17, 2016 at 21:26 | history | edited | PolyGeo♦ | CC BY-SA 3.0 |
deleted 54 characters in body
|
| Jan 17, 2016 at 19:59 | answer | added | user55937 | timeline score: 1 | |
| Jan 17, 2016 at 17:03 | comment | added | fdonnelly | Essentially what this person was looking to do, except I can't figure out how to do this within a GRASS Python script: gis.stackexchange.com/questions/7038/… | |
| Jan 17, 2016 at 17:01 | comment | added | fdonnelly | I don't think so. For commands that return strings as output, like g.region, read_command returns the result as an unparsed string: gis.stackexchange.com/questions/74549/…. I want to capture any message that's printed or returned to the output window or shell. | |
| Jan 16, 2016 at 22:12 | comment | added | user55937 | Is read_command what you're looking for? | |
| Jan 15, 2016 at 21:45 | history | asked | fdonnelly | CC BY-SA 3.0 |