Modify path->perspective is broken

Is this an issue with the numpy version in Suse Linux 10.1?

What is the numpy version in Suse Linux 10.1?

A related issue is that the extension doesn't disable itself at launch if numpy is not installed at launch (as other extensions, like the latex formula extension do, if their dependencies are not present). Running the effect gives the error:

Inkscape has received additional data from the script executed. The script did not return an error, but this may indicate the results will not be as expected.
Failed to import the numpy or numpy.linalg modules. These modules are required by this extension. Please install them and try again.

This extension works fine on my system. (Fedora core 6, Inkscape latest SVN, numpy version 1.0.3 installed just now by yum from Fedora project). Marking incomplete until we can get enough information to confirm the bug.

I also got the numpy.linalg error on fedora 7, but it all worked fine after installing numpy 1.0.3

On WinXP I get errors with perspective.py and inkex.py but Im not sure if its related to this bug

Hi Prkos,
Do you mean you got the original numpy.linalg error ("... ImportError: /usr/lib/libblas.so.3: undefined symbol: _gfortran_st_write ...") or the ('Failed to import numpy or nump.linalg") error that I got ?

I meant the latter: Failed to import numpy.linalg.... Please install it from a website blah blah.....

Something like that :)

Well, I think that message (numpy not installed, blah blah...) is not a bug, although it would be nice if perspective would check for its dependencies at load time. I'm going to leave this incomplete (hoping it will just die a natural death of expiring) since no one has been able to confirm the original error.

Well the extension _does_ check for its deps when it (the extension) is launched, that's where the message comes from. Inkscape doesn't have facilities for checking if python modules are or are not installed. This would be necessary if Inkscape were to disable an extension when it (the Inkscape applicaiton) is launched. It feels odd to suggest that Inkscape itself should become aware of available python modules, because the external extensions are language agnostic. It may be better to create some method for an extension to check its own deps and report that information to inkscape. I suggest each extension come with a separate executable which only checks deps and reports success or failure via exit status code. In the inx file we could have a property for dependency check application. Of course, this could have very negative effects on the start time for the inkscape application.

The original error does not appear to be a bug in Inkscape either. The version of libblas is missing a function needed by numpy.linalg. Likely libblas is too old of a version or it was configured with out support of the needed functionality.

I think this can then be marked as Invalid

Im satisfied with getting the message about whats missing, its easy to fix and its not strictly Inkscape bug.

Agreed that this looks invalid -- regarding Aaron's suggestion about checking for deps, I was going on the nice behavior of LaTeX formula extension, which checks whether latex, dvips, etc are available on the path, and hides itself if they're not.

On the other hand, leaving the extensions in there, with informative errors about missing dependencies helps users discover new features. Low-priority in any event...

Right! latex and dvips are programs that can be found in the path by the OS and therefore inkscape. the existence of numpy can only reliably be detected by python. I think this is probably wishlist-able. We'll have to talk to Ted. Giving extensions more flexible means to declare if they can find all their deps is a really good idea. There are numerous problems trying to test even for simple deps in a reliable crossplatform manner.