[GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
GRASS GIS
trac at osgeo.org
Thu Dec 17 00:30:28 PST 2020
#2895: Define dependencies for GRASS addons
--------------------------+-------------------------
Reporter: pmav99 | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.8.3
Component: Default | Version: unspecified
Resolution: | Keywords: g.extension
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by sbl):
Pyhon modules are supposed to use lazy imports and should catch if a
required python library is available at runtime. The same should be true
for dependency on other addons (should probably added to the SUBMITTING
guidelines).
For C modules, installation of libraries through g.extension is probably
not very straight forward.
So the question is a bit, where this is supposed to be handeled.
Personally, I would probably prefer if the addon itself catches evtl.
missing dependencies and gives a clear error message. Silently installing
stuff can be a bit scary...
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:19>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list