[GRASS-dev] grass python module

Martin wrote:
> I would suggest splitting grass.py into several modules,

Glynn wrote:

This would be a good point to consider how it relates to
the SWIG interface.

....

Or should we make them equal and just have grass.script.vector
and grass.swig.vector?

And should "swig" even be visible, or should it be e.g.
"grass.lib.vector"?

very nice ideas guys.
grass.lib.vector and grass.script.vector sound good.
(possibly use a more descriptive name for 'script'?)

Hamish

Hamish wrote:

(possibly use a more descriptive name for 'script'?)

"script" seems quite accurate; most of what it does is running
external commands, which is what "scripting" means (there's a
difference between a "script" and an "interpreted program").

--
Glynn Clements <glynn@gclements.plus.com>