On Sun, Feb 04, 2018 at 07:16:14PM +0100, Maren Hachmann wrote:
Then we would need to do the same for all the other extensions that use numpy, too. There are lots of those.
I know there has been talk about separating extensions out into their own packages - but I got the impression that's more or less a long term solution, for which we lack volunteers... and not a solution that will help with 0.92.3, or probably even 0.93.
(or would anyone be interested in separating extensions out?)
Would a short term fix via error message be okay, until something like that happens?
If people thinks moving a bunch of /usr/share/inkscape/extensions/foo.py files in its own binary package (say, inkscape-extensions-blah), that's trivial to do, and I could do it even now, but would it really help?
Then that package would a recommendency itself, so people installing 'inkscape' on a Mint box wouldn't get the extension and then complain again about that as well.
IMHO, having the extension catch the failed numpy import and gracefully error out saying "to use this thing you need to install the python(3?) numpy module" is a very fine final solution.