[GRASS-user] problems compiling grass 7

Martin Landa landa.martin at gmail.com
Fri Jun 19 04:55:53 EDT 2009


2009/6/19 G. Allegri <giohappy at gmail.com>:
>> Sorry; the __init__.py files for the packages need to exist, but they
>> shouldn't import the modules/packages. As it stands,
>> "import grass.lib.grass" will load *all* of the binary modules, and
>> all of their dependencies (i.e. including GDAL, and all of its
>> dependencies).
> I'm new to grass 7 and it's python support. A question: the lib module
> is supposed to offer what? In my build it's empty...

It's Python Swig interface for GRASS libraries. See examples in swig/python.

>> The __init__.py files are supposed to contain an __all__ array listing
>> the modules and/or sub-packages. This matters on Windows, so that e.g.
>> "from grass.lib import *" imports the modules with the correct case in
>> the event that the filesystem entries have been converted to
>> upper-case or camel-case.
> +1 for the __all__ statement.

yes, how to dynamically add "lib" to __all__ list when swig/python is
build successfully?


Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

More information about the grass-user mailing list