Send grass-windows mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.osgeo.org/mailman/listinfo/grass-windows
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-windows digest..."
Today's Topics:
1. Re: No such file or directory (Glynn Clements)
2. wingrass and ArcGIS with Python (Helena Mitasova)
3. Re: wingrass and ArcGIS with Python (Peter Brooks)
4. Re: [GRASS-dev] Re: [GRASS-windows] No such file or directory
(Peter Brooks)
----------------------------------------------------------------------
Message: 1
Date: Sat, 15 Aug 2009 02:24:58 +0100
From: Glynn Clements <[email protected]>
Subject: Re: [GRASS-windows] No such file or directory
To: Peter Brooks <[email protected]>
Cc: Markus Neteler <[email protected]>, [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Peter Brooks wrote:
> No, I think it is whitespace... I'm trying to use the 'cmd >' field
> in the 'GRASS GIS Layer Manager' (the new wxPython GUI). I guess
> this is what a Windows user would try to do :-)
>
> I tried adding a space to the folder name (= 'c:\nc external'),
> forward slashes don't help but speech or quote marks do.
>
> (I think the same thing happens with all r.in commands if they are
> looking for external files - is this to be expected?)
If an option expects a filename, it will typically be passed directly
to open(), fopen() etc. If you supply a plain filename or a relative
path, it will be interpreted relative to the current directory (rather
than e.g. the mapset directory).
If an option value contains whitespace, it needs to be quoted
appropriately for the context in which it occurs.
In a Windows command prompt, you need to put double quotes around the
entire option=value argument.
In bash, you can use single or double quotes around the entire
argument or around the filename, or precede spaces by backslash
characters (also, you need to either use forward slashes as directory
separators or quote backslashes appropriately).
The command prompt in the wxPython GUI uses Python's shlex module (in
POSIX mode), which provides bash-like quoting:
http://docs.python.org/library/shlex.html#parsing-rules
Filenames entered elsewhere in the GUI shouldn't normally need to be
quoted.
Even with correct quoting, some shell scripts may not correctly handle
filenames containing spaces; this is part of the reason why shell
scripts have been replaced with Python scripts in GRASS 7.
--
Glynn Clements <[email protected]>
------------------------------
Message: 2
Date: Fri, 14 Aug 2009 23:06:06 -0400
From: Helena Mitasova <[email protected]>
Subject: [GRASS-windows] wingrass and ArcGIS with Python
To: [email protected]
Cc: GRASS developers list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
For those who need to run both ArcGIS and GRASS with Python (common
situation in GIS labs),
here is the solution for the reported problem from our technical
support:
I found there are different builds of winpython 2.5 . The version
that works for both is build is 212. I found it here...
http://sourceforge.net/projects/pywin32/files/pywin32/Build%20212/
pywin32-212.win32-py2.5.exe/download
Helena
>
> Message: 1
> Date: Thu, 6 Aug 2009 21:44:23 -0400
> From: Helena Mitasova <[email protected]>
> Subject: [GRASS-windows] Re: [GRASS-dev] wingrass on VISSTA and XP
> with two pythons
> To: [email protected]
> Cc: GRASS developers list <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Just an update, in case somebody else has a similar problem -
> GRASS from OSGeo4W installer runs with nviz on the same VISTA
> computers
> that had the problem below.
>
> But we got an interesting issue with the native installer on our XP
> machines in the teaching lab.
> After a separate Python2.5 install GRASS wxpython does not run anymore
>
> The error message says:
> python.exe
> the procedure entry point ?
> PyWinObject_AsHABDLE@@YAHPAU_object@@pa...@z
> could not be located in the dynamic link library pywintypes25.dll
>
> when we searched for pywintypes25.dll we got
> C:\GRASS6-6-SVN\extralib 112KB 1/11/2009
> C:\WINDOWS\system32 100KB 9/22/2006
> C:\Python25\Lib\site_packages\ 100KB 9/22/2006
> C:\GRASS6-6-SVN\Python25\Lib 112KB 1/11/2009
>
> so it looks like the C:\Python25\Lib\site_packages version
> is different from the one used by GRASS I asssume that the problem
> we have is that GRASS is looking into the wrong pywintypes25.dll.
> Is there a solution to this? So far it looks like removing the second
> install of Python2.5 is not an option.
>
> thanks,
>
> Helena
>
>
>
> On Aug 6, 2009, at 11:02 AM, Helena Mitasova wrote:
>
>> Has anybody installed the latest install on VISSTA?
>> we get only the first two icons and no Tcltk runs (that means no
>> nviz)
>>
>> http://grass.osgeo.org/grass64/binary/mswindows/native/
>> WinGRASS-6.4.0SVN-r38537-1-Setup.exe
>>
>> thanks,
>>
>> Helena_______________________________________________
>> grass-dev mailing list
>> [email protected]
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
>
> ------------------------------
>
> _______________________________________________
> grass-windows mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/grass-windows
>
>
> End of grass-windows Digest, Vol 36, Issue 2
> ********************************************
------------------------------
Message: 3
Date: Sat, 15 Aug 2009 10:38:56 +0100
From: "Peter Brooks" <[email protected]>
Subject: Re: [GRASS-windows] wingrass and ArcGIS with Python
To: Helena Mitasova <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII
(I can't cc this to the developers list - I'm not subscribed).
I use ArcMap as well - I initially had a problem running either GRASS
or the QGIS GRASS plugin (sorry, I can't remember which) and ended up
copying the pywintypes25.dll version 2.5.212.0 file into the
windows\system32 folder (after renaming the existing version, which
was 2.5.214.0).
Hope this helps someone...
Cheers
Peter
On 14 Aug 2009 at 23:06, Helena Mitasova wrote:
For those who need to run both ArcGIS and GRASS with Python (common
situation in GIS labs), here is the solution for the reported problem
from our technical support:
I found there are different builds of winpython 2.5 . The version
that works for both is build is 212. I found it here...
http://sourceforge.net/projects/pywin32/files/pywin32/Build%20212/
pywin32-212.win32-py2.5.exe/download
Helena
>
> Message: 1
> Date: Thu, 6 Aug 2009 21:44:23 -0400
> From: Helena Mitasova <[email protected]>
> Subject: [GRASS-windows] Re: [GRASS-dev] wingrass on VISSTA and XP
> with two pythons To: [email protected] Cc: GRASS
> developers list <[email protected]> Message-ID:
> <[email protected]> Content-Type:
> text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Just an update, in case somebody else has a similar problem -
> GRASS from OSGeo4W installer runs with nviz on the same VISTA
> computers that had the problem below.
>
> But we got an interesting issue with the native installer on our XP
> machines in the teaching lab. After a separate Python2.5 install
> GRASS wxpython does not run anymore
>
> The error message says:
> python.exe
> the procedure entry point ?
> PyWinObject_AsHABDLE@@YAHPAU_object@@pa...@z
> could not be located in the dynamic link library pywintypes25.dll
>
> when we searched for pywintypes25.dll we got
> C:\GRASS6-6-SVN\extralib 112KB 1/11/2009
> C:\WINDOWS\system32 100KB 9/22/2006
> C:\Python25\Lib\site_packages\ 100KB 9/22/2006
> C:\GRASS6-6-SVN\Python25\Lib 112KB 1/11/2009
>
> so it looks like the C:\Python25\Lib\site_packages version
> is different from the one used by GRASS I asssume that the problem
> we have is that GRASS is looking into the wrong pywintypes25.dll. Is
> there a solution to this? So far it looks like removing the second
> install of Python2.5 is not an option.
>
> thanks,
>
> Helena
>
>
>
> On Aug 6, 2009, at 11:02 AM, Helena Mitasova wrote:
>
>> Has anybody installed the latest install on VISSTA?
>> we get only the first two icons and no Tcltk runs (that means no
>> nviz)
>>
>> http://grass.osgeo.org/grass64/binary/mswindows/native/
>> WinGRASS-6.4.0SVN-r38537-1-Setup.exe
>>
>> thanks,
>>
>> Helena_______________________________________________
>> grass-dev mailing list
>> [email protected]
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
>
> ------------------------------
>
> _______________________________________________
> grass-windows mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/grass-windows
>
>
> End of grass-windows Digest, Vol 36, Issue 2
> ********************************************
_______________________________________________
grass-windows mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-windows
------------------------------
Message: 4
Date: Sat, 15 Aug 2009 10:45:04 +0100
From: "Peter Brooks" <[email protected]>
Subject: Re: [GRASS-dev] Re: [GRASS-windows] No such file or directory
To: Hamish <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII
The 'About' window says
GRASS GIS 6.4.0svn (2009)
GIS Library Revision 37101 (2009-05-10)
I downloaded and installed on 02-Aug.
Cheers
Peter
On 14 Aug 2009 at 16:54, Hamish wrote:
> [r.in.poly fails to read text input file on Windows/CMD line]
I have checked at the r.in.poly source code, the problem does
not seem to be there. The path is passed to fopen() verbatim.
what version/revision of 6.4.0svn is this? is it the latest?
ISTR that Martin&Glynn had fixed this -- wxGUI now uses a
python parser which understands shell quoting on the Cmd> line.
But that might only be present in the very latest build.
Hamish
------------------------------
_______________________________________________
grass-windows mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-windows
End of grass-windows Digest, Vol 36, Issue 7
********************************************
