Hi,
I would suggest splitting grass.py into several modules, e.g.
general
raster
vector
database
User could import only desired modules from 'grass' package, e.g.
from grass import raster
?
Martin
--
Martin Landa * http://gama.fsv.cvut.cz/~landa
On Fri, May 8, 2009 at 1:57 PM, Martin Landa wrote:
> Hi,
>
> I would suggest splitting grass.py into several modules, e.g.
>
> general
> raster
> vector
> database
>
> User could import only desired modules from 'grass' package, e.g.
>
> from grass import raster
Sounds good to me (and move out t
Martin Landa wrote:
> I would suggest splitting grass.py into several modules, e.g.
>
> general
> raster
> vector
> database
>
> User could import only desired modules from 'grass' package, e.g.
>
> from grass import raster
This would be a good point to consider how it relates to the SWIG
int
> 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
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
Hi,
2009/5/8 Glynn Clements :
[...]
> Currently, those modules are named swig.grass, swig.vector, etc. That
> was done to avoid a collision over "import grass". But "swig" is a
> rather generic prefix to use. I had thought about changing it from
> "swig.*" to "grass.*", and renaming "grass" to e
On Fri, May 22, 2009 at 12:14 AM, Martin Landa wrote:
> 2009/5/8 Glynn Clements :
>
> [...]
>
>> Currently, those modules are named swig.grass, swig.vector, etc. That
>> was done to avoid a collision over "import grass". But "swig" is a
>> rather generic prefix to use. I had thought about changing
