On 25/11/09 17:45, m h wrote:
On Wed, Nov 25, 2009 at 5:55 AM, ~suv <suv-sf@...16...> wrote:
On 25/11/09 12:49, Joshua Facemyer wrote:
Joshua A. Andler wrote:
On Wed, 2009-11-25 at 01:12 +0000, Gary Hawkins wrote:
Thanks for the update - anyone know when/if the extensions will be fixed (or how to fix them)?
snip
It is a known issue, but it had appeared to the packager that it was (magically and unknown how) fixed with the 0.47 final package. I'm sorry to hear that it wasn't. As to when it will be fixed, that will be when someone with knowledge has time to sit down and figure it out.
Isn't this as simple as installing python-lxml? Whether it's readily available on OSX is a different question, though...
I can see how the numpy dependency might be nice for some plugins. However for basic xml manipulation why rely on a 3rd party one? Most modern OS's that ship with python versions that include etree out of the box...
(I'm not sure what happens on windows with the python stuff)
These distributed extensions use numpy:
LeWitt:Inkscape-SVN suv$ grep -i numpy Inkscape.app/Contents/Resources/extensions/*.py | cut -d : -f 1 - | sort | uniq Inkscape.app/Contents/Resources/extensions/dxf_outlines.py Inkscape.app/Contents/Resources/extensions/perspective.py Inkscape.app/Contents/Resources/extensions/polyhedron_3d.py LeWitt:Inkscape-SVN suv$
If the 'numpy' dependency of these three could be replaced by native python functions that work in all supported python versions (2.3-2.6) - I'm sure it would be welcomed as patch for the current SVN branch ;-)
OTOH I have no idea how many third-party extensions rely on 'numpy' being available on all supported platforms - AFAIK the 'numpy' module is included in the win32 installer (which installs its own Python 2.5 binary) and in the osx packages for 0.46 and 0.47 (which currently includes the modules for python 2.3-2.5 PPC and 2.3-2.6 i386)
~suv