Naming conventions for imports in GRASS codebase
|Reported by:||pmav99||Owned by:|
There is a great deal of variation in the way that grass code does imports. Just a few examples:
import grass.script as core import grass.script as gcore import grass.script as grass import grass.script as gs import grass.script as gscript import grass.script as sgrass import grass.script.core as core import grass.script.core as gcore import grass.script.core as grass import grass.script.core as gscore import grass.script.raster as grast import grass.script.raster as raster import grass.pygrass.utils as gutils import grass.pygrass.utils as utils import grass.lib.gis as gislib import grass.lib.gis as libgis
I think it would be a good idea if a certain style was picked and consistently used throughout the codebase.