<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-3" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 14/12/2009 18:17, Glynn Clements wrote:
<blockquote
cite="mid:19238.29468.73846.264038@cerise.gclements.plus.com"
type="cite">
<pre wrap="">Luigi Ponti wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">But when I do /db.test test1/ errors arise:
</pre>
</blockquote>
<pre wrap="">
[...]
My guess is that this is a problem with Cygwin and Windows 7.
</pre>
</blockquote>
<pre wrap="">I have eventually reverted back to GRASS 6.3.0 for now, after fixing
some missing dll's. I am not sure what is wrong with 6.4 vs 6.3 but I
need a functional GRASS/Cygwin version to run some bash scripts while I
port them to Phython.
</pre>
</blockquote>
<pre wrap=""><!---->
I wouldn't consider the supplied db.test test case failing to equate
to "non-functional"; it's the test case which is wrong, not db.select.
</pre>
</blockquote>
You are right: I used the wrong words -- thanks for the explanation. I
will keep trying to get 6.4.0-RC5 compiled on Cygwin/Windows 7. Thanks
again for sharing your configure options.<br>
<br>
<blockquote
cite="mid:19238.29468.73846.264038@cerise.gclements.plus.com"
type="cite">
<pre wrap="">[...]
If you care about the exact format of floating-point values output
from db.select, note that future versions will behave like 6.4.0-RC5,
not like 6.3.x.
</pre>
</blockquote>
Good to know, thanks.<br>
<blockquote
cite="mid:19238.29468.73846.264038@cerise.gclements.plus.com"
type="cite">
<blockquote type="cite">
<pre wrap="">Also, is it even possible to do Python scripting in the native Windows
GRASS 6.4.x?
</pre>
</blockquote>
<pre wrap=""><!---->
Yes.
</pre>
<blockquote type="cite">
<pre wrap="">For example, I noticed that some of the GRASS scripts that
have been translated to Python require a grass.py package, which I don't
see in my osgeo4w installation.
</pre>
</blockquote>
<pre wrap=""><!---->
There is no grass.py. It existed for a brief time, but the "grass"
module was replaced with a "grass" package containing multiple
modules, then later split into two subpackages, "script" and "lib".
</pre>
</blockquote>
The package is described in the programming manual -- I should have
explored better:<br>
<a class="moz-txt-link-freetext" href="http://download.osgeo.org/grass/grass6_progman/pythonlib.html">http://download.osgeo.org/grass/grass6_progman/pythonlib.html</a><br>
<br>
The progman page above says that the code is in lib/python/ while in my
osgeo4w GRASS 6.4.0svn r36506<br>
<a class="moz-txt-link-freetext" href="http://trac.osgeo.org/osgeo4w/wiki/pkg-grass">http://trac.osgeo.org/osgeo4w/wiki/pkg-grass</a><br>
<br>
the code seems to reside into etc/python.<br>
<blockquote
cite="mid:19238.29468.73846.264038@cerise.gclements.plus.com"
type="cite">
<pre wrap="">
The change was made to accomodate the SWIG bindings for the GRASS
libraries in the "grass.lib" package, so the scripting functions were
moved from "grass" to "grass.script".
</pre>
</blockquote>
Would the lib subpackage you mentioned be any useful in developing
GRASS scripts? (I could not find it in my osgeo4w installation.)<br>
Thanks and regards,<br>
Luigi<br>
<blockquote
cite="mid:19238.29468.73846.264038@cerise.gclements.plus.com"
type="cite">
<pre wrap="">
Some early scripts use "import grass", but for current versions
(including 6.4.0-RC5), you need e.g. "import grass.script as grass".
</pre>
</blockquote>
<br>
</body>
</html>