#2291: Python not quitting on exit
---+
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.1.0
I think in the long term it would be better to change the raster directory
structure such that raster and vector have the same mapset/(raster,
vector)/mapname/element path. Then we would be able to move some useful
element related functions from librast to libgis.
Huidae
On May 13, 2014 5:11 PM, "
Huidae Cho wrote:
> I agree. Maybe, Markus M has a better idea why we needed r60149?
AFAICT, the reason for the logic change is so that it doesn't print a
warning if the file simply doesn't exist.
The previous version would only call G_find_file2() if the mapset
couldn't otherwise be determined
Does anybody have experience with the scikit-learn toolkit? It seems like a
very extensive tool set for machine learning in Python. I have no
experience in programming in Python, so I cannot really judge how difficult
it would be to call functions from this tool set in GRASS, but if possible,
that
Markus Neteler wrote:
> I tried my current start-python-and-create-a-location script on Windows.
> The location is generated but then a call of the scripting library fails
> with a gettext error (I print the os.environment to understand more but no
> idea):
> "C:\OSGeo4W\apps\grass\grass-7.1.svn
#2284: Keep pressing Ctrl+C in command line
--+-
Reporter: hcho | Owner: grass-dev@…
Type: enhancement | Status: reopened
Priority: normal | Milestone:
Huidae Cho wrote:
> Ok, Let me understand it. So the keyboard interrupted exception is coming
> from prompt.py, not from grass.py.
Yes; from the original bug report:
> ^CTraceback (most recent call last):
> File "/home/grass/trunk/dist.x86_64-unknown-linux-gnu/etc/prompt.py",
I agree. Maybe, Markus M has a better idea why we needed r60149?
On Tue, May 13, 2014 at 2:08 PM, Martin Landa wrote:
> Hi,
>
> 2014-05-13 20:06 GMT+02:00 Huidae Cho :
> > but in trunk, r60149 replaced it with
>
> then we should discuss about backporting such change instead of quick
> fixing in
Hi,
2014-05-13 20:06 GMT+02:00 Huidae Cho :
> but in trunk, r60149 replaced it with
then we should discuss about backporting such change instead of quick
fixing in relbr70 (without explanation)... Martin
___
grass-dev mailing list
grass-dev@lists.osgeo.
In 70release, we had
else if (!mapset || !*mapset)
mapset = G_find_file2(element, name, mapset);
but in trunk, r60149 replaced it with
mapset = G_find_file2(element, name, mapset);
and G_find_file2 hates an empty name.
Huidae
On Tue, May 13, 2014 at 12:24 PM, GRASS GIS wrote:
Hi,
I tried my current start-python-and-create-a-location script on Windows.
The location is generated but then a call of the scripting library fails
with a gettext error (I print the os.environment to understand more but no
idea):
Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit
#2289: v.colors not working
-+--
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: reopened
Priority: normal | Milestone: 7.0.0
Oh! I got it. Thanks, Markus.
On Tue, May 13, 2014 at 10:56 AM, GRASS GIS wrote:
> #2289: v.colors not working
>
> -+--
> Reporter: veroandreo | Owner: grass-dev@…
> Type: defect | Status: reope
#2289: v.colors not working
-+--
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: reopened
Priority: normal | Milestone: 7.0.0
#2289: v.colors not working
-+--
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.0.0
#2290: Grass not starting
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.0
Comp
#2290: Grass not starting
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.0
Comp
#2290: Grass not starting
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.0
Comp
#2289: v.colors not working
-+--
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.1.0
The bug was reported (r60164) before my changes to the monitors (r60204) and
is not related to my recent work.
I fixed this bug in r60225.
Huidae
On Tue, May 13, 2014 at 6:06 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:
> On 13/05/14 04:04, Veronica Andreo wrote:
>
>> Dear all,
>>
#2289: v.colors not working
+---
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.1.0
On 13/05/14 04:04, Veronica Andreo wrote:
Dear all,
Is something wrong with v.colors? I'm not able to colorize anything, it
does say it sets the corresponding color table, but then... just grey...
v.colors map=soils_general@PERMANENT use=cat color=wave
d.mon wx0
d.vect soils_general ---> no col
22 matches
Mail list logo
