[GRASS-dev] [GRASS GIS] #2327: r.diversity = Illegal areas disposition

2014-06-06 Thread GRASS GIS
#2327: r.diversity = Illegal areas disposition -+-- Reporter: sands| Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone:

Re: [GRASS-dev] [GRASS-SVN] r60703 - in grass/trunk: display/d.vect general/g.gisenv gui/wxpython/animation lib/python/temporal raster/r.colors raster/r.external raster/r.in.bin raster/r.mapcalc raste

2014-06-06 Thread Glynn Clements
Huidae Cho wrote: I was thinking about the same thing. Maybe add char *exclusive_group to Option and Flag and G_parser() takes care of exclusiveness? There are two relatively straightforward cases for option interdependencies: 1. At most one option from a set may be provided (mutual

Re: [GRASS-dev] [GRASS-SVN] r60679 - grass/trunk/lib/python/script

2014-06-06 Thread Moritz Lennert
On 05/06/14 21:14, Martin Landa wrote: Hi, 2014-06-05 17:36 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be: ... this would follow the apparently working method in GRASS 6. Maybe worth a try also in GRASS 7 at this point. I had the feeling that this was the consensus (or at least with

Re: [GRASS-dev] [GRASS-SVN] r60679 - grass/trunk/lib/python/script

2014-06-06 Thread Glynn Clements
Markus Neteler wrote: 1. GRASS 7 will need .bat wrappers for Python scripts on Windows. That has the same issues as using shell=True, but at least it only applies in the case where we're executing a script. ... this would follow the apparently working method in GRASS 6. Maybe worth a

Re: [GRASS-dev] Enhancement request: print name(s) of generated map(s) upon completion

2014-06-06 Thread Moritz Lennert
On 05/06/14 22:38, Markus Neteler wrote: On Thu, Jun 5, 2014 at 9:28 PM, Rashad M mohammedrasha...@gmail.com wrote: Hi, I would like to add a +1 to Mortiz here. This enhancement should be in the verbose. Like there are debug level for message. These message can be like level in verbose. say

Re: [GRASS-dev] [GRASS-SVN] r60679 - grass/trunk/lib/python/script

2014-06-06 Thread Glynn Clements
Martin Landa wrote: ... this would follow the apparently working method in GRASS 6. Maybe worth a try also in GRASS 7 at this point. I had the feeling that this was the consensus (or at least with lack of clear dissension) we had reached: consensus is somehow courageous to say,

Re: [GRASS-dev] [GRASS GIS] #2326: Command functions in grass.script.core miss a correct error reporting

2014-06-06 Thread GRASS GIS
#2326: Command functions in grass.script.core miss a correct error reporting -+-- Reporter: wenzeslaus | Owner: grass-dev@… Type: enhancement | Status: new Priority:

Re: [GRASS-dev] [GRASS GIS] #2326: Command functions in grass.script.core miss a correct error reporting

2014-06-06 Thread GRASS GIS
#2326: Command functions in grass.script.core miss a correct error reporting -+-- Reporter: wenzeslaus | Owner: grass-dev@… Type: enhancement | Status: new Priority:

Re: [GRASS-dev] [GRASS-SVN] r60713 - in grass/trunk: include lib/gis

2014-06-06 Thread Glynn Clements
Author: hcho Date: 2014-06-05 10:32:48 -0700 (Thu, 05 Jun 2014) New Revision: 60713 Modified: grass/trunk/include/gis.h grass/trunk/lib/gis/parser.c Log: The exclusive member of the Option and Flag structures is a comma-separated string. Whitespaces are not ignored.

Re: [GRASS-dev] [GRASS GIS] #2326: Command functions in grass.script.core miss a correct error reporting

2014-06-06 Thread GRASS GIS
#2326: Command functions in grass.script.core miss a correct error reporting -+-- Reporter: wenzeslaus | Owner: grass-dev@… Type: enhancement | Status: new Priority:

Re: [GRASS-dev] [GRASS GIS] #2326: Command functions in grass.script.core miss a correct error reporting

2014-06-06 Thread GRASS GIS
#2326: Command functions in grass.script.core miss a correct error reporting -+-- Reporter: wenzeslaus | Owner: grass-dev@… Type: enhancement | Status: new Priority:

Re: [GRASS-dev] [GRASS-SVN] r60713 - in grass/trunk: include lib/gis

2014-06-06 Thread Martin Landa
2014-06-06 9:52 GMT+02:00 Glynn Clements gl...@gclements.plus.com: Reverted. This issue warrants an actual discussion. A discussion which I've been trying to have for *years*. cool Glynn! Please could you provide your solution at least or you will just continue reverting other people work in

Re: [GRASS-dev] [GRASS-SVN] r60713 - in grass/trunk: include lib/gis

2014-06-06 Thread Martin Landa
2014-06-06 12:52 GMT+02:00 Martin Landa landa.mar...@gmail.com: 2014-06-06 9:52 GMT+02:00 Glynn Clements gl...@gclements.plus.com: This issue warrants an actual discussion. A discussion which I've been trying to have for *years*. I remember some mails at ML some years ago, but without any

Re: [GRASS-dev] [GRASS GIS] #2258: t.create creates DB always in the PERMANENT

2014-06-06 Thread GRASS GIS
#2258: t.create creates DB always in the PERMANENT -+-- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: normal |

Re: [GRASS-dev] [GRASS-SVN] r60713 - in grass/trunk: include lib/gis

2014-06-06 Thread Huidae Cho
All, I can feel strong frictions between Glynn and some of us. I was shocked when Glynn simply broke 7.1 on Windows. From my experience, I can see that he is more of a purist and doesn't like workarounds and hacks. I totally understand his points, but just because there is an issue doesn't make

Re: [GRASS-dev] [GRASS-SVN] r60713 - in grass/trunk: include lib/gis

2014-06-06 Thread Sören Gebbert
Hi, just to add my 2 cent: 2014-06-06 16:35 GMT+02:00 Huidae Cho gras...@gmail.com: All, I can feel strong frictions between Glynn and some of us. I was shocked when Glynn simply broke 7.1 on Windows. From my experience, I can see that he is more of a purist and doesn't like workarounds and

Re: [GRASS-dev] [GRASS-SVN] r60713 - in grass/trunk: include lib/gis

2014-06-06 Thread Glynn Clements
Martin Landa wrote: This issue warrants an actual discussion. A discussion which I've been trying to have for *years*. I remember some mails at ML some years ago, but without any *real* outcome (wiki page, see for RFC's from GDAL project). Simply *nothing* happen during the last years.

Re: [GRASS-dev] g.mlist list multiple types from all mapsets

2014-06-06 Thread Vaclav Petras
On Tue, Jun 3, 2014 at 3:43 AM, Huidae Cho gras...@gmail.com wrote: I tested g.mlist with the attached script. I started from test_g_list.py and replaced g.list with g.mlist -p and g.list -f with g.mlist -f. g.mlist passed the test, which means g.list == g.mlist -p g.list -f == g.mlist -f.

Re: [GRASS-dev] [GRASS-SVN] r60713 - in grass/trunk: include lib/gis

2014-06-06 Thread Glynn Clements
Huidae Cho wrote: I can feel strong frictions between Glynn and some of us. I was shocked when Glynn simply broke 7.1 on Windows. From my experience, I can see that he is more of a purist and doesn't like workarounds and hacks. I totally understand his points, but just because there is an

Re: [GRASS-dev] GRASS 7.0beta3 planning

2014-06-06 Thread Markus Neteler
On Sun, May 25, 2014 at 11:23 PM, Markus Neteler nete...@osgeo.org wrote: Hi, as Martin stated in a recent ticket comment, beta3 should be released asap. I would like to get first the pygrass changes backported (not difficult including the manual improvements). Maybe we skip the pygrass

Re: [GRASS-dev] 6.4.4 planning

2014-06-06 Thread Markus Neteler
On Thu, Jun 5, 2014 at 5:47 PM, Moritz Lennert moritz.lenn...@ulb.ac.be wrote: ... As I've already told Markus off-list, I think that in order for this to work we would need a clearly defined release-process with clear announcements of the different steps (pre-freeze warning sufficiently early,

Re: [GRASS-dev] GRASS 7.0beta3 planning

2014-06-06 Thread Vaclav Petras
On Fri, Jun 6, 2014 at 3:41 PM, Markus Neteler nete...@osgeo.org wrote: Maybe we skip the pygrass sphinx docs for RC3? Anyway we mostly focus on the online documentation being up to date, right? ... the OSGeoLive feature freeze for the FOSS4G Portland conf is upcoming. This would be nice.

[GRASS-dev] Week 3: GRASS GIS 3D flowlines

2014-06-06 Thread Anna Petrášová
Hi all, 1. What did you get done this week: I have a prototype generating flowlines, I tested it so far on artificial data. More on the wiki [1]. The code is here [2]. 2. What do you plan on doing next week? I would like to test it on different data and implement 3D flow accumulation. 3. Are

[GRASS-dev] gsoc2014 grass metadata week 3

2014-06-06 Thread Matej Krejci
Hi all, Below is my weekly report: *Work done* Consulted design of metadata editor with mentors. Consulted current implementation of v.info.iso and r.info.iso Search for alternatives to Jinja templates (current implementation) Learned basics of wxPython *Work to be done in the next week* For

Re: [GRASS-dev] [GRASS GIS] #2258: t.create creates DB always in the PERMANENT

2014-06-06 Thread GRASS GIS
#2258: t.create creates DB always in the PERMANENT -+-- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: normal |