On Sun, Jan 06, 2008 at 06:00:41PM -0600, Aaron Spike wrote:
Bryce Harrington wrote:
It doesn't work for me either, but I see the following text:
The fantastic lxml wrapper for libxml2 is required by inkex.py and therefore this extension. Please download and install the latest version from http://cheeseshop.python.org/pypi/lxml/.
All the python goo probably ought to be repackaged separately or something. Otherwise the Inkscape Ubuntu package will pull in half the world to try getting every extension working. ;-)
Most if not all of the python effects python-lxml. A few require numpy. Other effect can require certain other executables like gimp, pstoedit, dvips and latex but these effects are disabled and report the missing dep in the effects error log. We don't currently have a method of determining which language specific libs an effect needs so we can't disable effects that require python libs. (If we want to do something like this perhaps we can have each effect supply a separate executible that will check for its own deps.) I think we can safely include the python effects and require lxml and maybe numpy without "pulling in half of the world". ;-)
Well both python-numpy and python-xml are included as recommends, and the package description already mentions python-xml. They could be made hard depends, but then people who do not want the extra libraries would be screwed. Plus, making those two hard depends would then just mask the true problem, as if there are additional libs that some effect would like, we're back in the same situation. Really, the effects need to be disabled if their pre-requisites are not installed.
The dialog box also provides the following information...
"Traceback (most recent call last): File "/usr/share/inkscape/extensions/perspective.py", line 127, in <module> e.affect() File "/usr/share/inkscape/extensions/inkex.py", line 153, in affect self.effect() File "/usr/share/inkscape/extensions/perspective.py", line 72, in effect q[query] = float(f.read()) ValueError: invalid literal for float():
I don't see those errors. Maybe report it as a bug if you're sure it's not due to your local system configuration.
I think it was do to the debug print messages. "Input::Input" isn't a valid literal for a python float. :-)
Weird, well that should be fixed.
Why does it say 'affect' instead of 'effect'? Typo?
Bryce