Thanks Hamish.<br>My desire was to make some benchmarking between different solutions...<br>I know Grass C low level modules do a lot of work, but as I'm not an experienced C programmer, I would prefer to do the same job (beyond scripting) with Python.
<br>A good reason, to me, to consider a SWIG solution is the possibility to make direct use of the huge quantity of Python packages available (as NumPy, wxPython, etc.), without loosing low level access to the Grass API.<br>
As you said, without the SWIG API, the most I can do is making system calls ("os.popen") to run Grass bash commands, with an unacceptable slowness and the obvious limitations it puts.<br>I think that the only solution is to start learning SWIG interface development by myself :-)
<br><br>Giovanni<br><br><br><div><span class="gmail_quote">2007/8/27, Hamish <<a href="mailto:hamish_nospam@yahoo.com">hamish_nospam@yahoo.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
G. Allegri wrote:<br>><br>> does anyone can make the point about Grass/Python SWIG interface<br>> development? I've seen in May the last changes on SVN made by Markus<br>> Neteler. Is the interface somehow ready to be used? Is there a roadmap in
<br>> the development?<br><br>Yes, it works, at a prototype stage. ie it may be rough around the edges<br>but basically works - it's at a stage where it needs testers & feedback<br>reports.<br><br>see<br> <a href="http://grass.gdf-hannover.de/wiki/GRASS_and_Python#Python-SWIG-GRASS_interface">
http://grass.gdf-hannover.de/wiki/GRASS_and_Python#Python-SWIG-GRASS_interface</a><br> <a href="http://mpa.itc.it/markus/grass63progman/swig/">http://mpa.itc.it/markus/grass63progman/swig/</a><br> <a href="http://thread.gmane.org/gmane.comp.gis.grass.devel/20751">
http://thread.gmane.org/gmane.comp.gis.grass.devel/20751</a><br> src/swig/python/README<br> src/swig/python/TODO<br> src/swig/python/test.py<br> src/swig/python/rasteraccess.py<br> src/swig/python/vectoraccess.py<br><br><br>
the subject of your email ("What's the point"?) touches on the reason I<br>personally haven't worked on python/swig further than getting it running-<br>even though I'd like to learn more python. To date I haven't been able to
<br>think of a time when I'd want to use it over writing a module directly in<br>C or scripting compiled modules in python without SWIG (as a replacement<br>for bash scripting). The low level grass modules give you a lot of
<br>control, so direct access to the C libgis functions isn't all that<br>critical.<br><br><br>good luck,<br>Hamish<br></blockquote></div><br>