This is a read-only archive of the inkscapeforum.com site. You can search for info here or post new questions and comments at System: Mac OS X 10.6 Snow Leopard Intel
Inkscape 0.47
All Effects fail with the famous message
<< 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/>, or install it through your package manager by a command like: sudo apt-get install python-lxml >>
I have scoured the numerous forum threads citing this msg, and the advice was always to install the Inkscape Python modules (even Python itself) by various means. I have downloaded the MacOSX Python dmg, but we seem to have everything needed...
At the command line, python --version yields 2.6.1
Apps/Inkscape 0.47/Contents/Resources/python/site-packages/i386/2.x/lxml/*
Apps/Inkscape 0.47/Contents/Resources/python/site-packages/i386/2.x/numpy/*
for both 2.5 and 2.6, both end directories populated with .py modules.
So why is Inkscape not finding them? Does it want them also in /Library/python (and if so, what is the exact subsequent directory heirarchy?). Where does Inkscape actually look for them?
TIA Lewis Smith
Inkscape 0.47 does not find Python Effects Mac OS X 10.6
-
lewyssmith
- Posts: 2
- Joined: Wed Mar 31, 2010 7:18 pm
-
lewyssmith
- Posts: 2
- Joined: Wed Mar 31, 2010 7:18 pm
Re: Inkscape 0.47 does not find Python Effects Mac OS X 10.6
~suv wrote:Bug #482993 in Inkscape: “Inkscape extensions do not work on MacOS X 10.6 (Snow Leopard)”
This succint reply led me to a working solution, for which many thanks. You have to follow trail upon trail! I came across threads already perused, but important new ones. Since it *is* an important issue, I cite what made Extensions work for us, which happens to be the neatest fix proposed:
At the command line:-
defaults write com.apple.versioner.python Version 2.5
which I imagine is just current user. For global use, Apple cite:-
defaults write /Library/Preferences/com.apple.versioner.python Version 2.5
May I comment on one of the Inkscape proposed fixes, which I find enigmatic - in http://wiki.inkscape.org/index.php/Gett ... ctsWorking ?
Binary packages - Python.packages.dmg
Directory heirarchies contained in the .dmg are:-
[ARCH]/ [VERSION]/lxml/*
[ARCH]/ [VERSION]/numpy/*
"Copy all the files & folders from the appropriate location to your Python site-packages directory ... /Library/Python/[VERSION]/site-packages on Leopard".
Note the Library heirarchy... So the Python VERSION exists twice in the proposed heirarchy. It all becomes mind-blowing: what exactly is one supposed to put where?
I also found enigmatic the setting of environment variables (along with, as an alternative to, the magic 'defaults write' commands) originally defined in Top
Re: Inkscape 0.47 does not find Python Effects Mac OS X 10.6
You misunderstand why I posted the link to bug #482993: this is a known and confirmed bug in Inkscape on Snow Leopard, but the bug is not fixed! i.e. there's no guaranteed solution to create a working Inkscape package and even less so how to fix it individually as a user. I posted the link to the bug report so you can track any progress that is made in fixing the issue, not to encourage you to try to solve it yourself - risking to break your python installation or other applications depending on it.
I don't and didn't recommend you trying to fix it yourself. It is clearly a problem that must be addressed and solved in the officially released Inkscape packages, not by the users themselves.lewyssmith wrote:I do not know MacOsX intimately; nor would most users.
I didn't.lewyssmith wrote:Thanks again for pointing to getting Inkscape working for us.
Re: Inkscape 0.47 does not find Python Effects Mac OS X 10.6
Offering my apologies for my rather impolite previous comment - sometimes I'm equally frustrated that there's no easy fix available for this problem. But I am convinced it needs to be solved at packaging level first - supporting individual Snow Leopard users trying to somehow fix a 'broken' (with regard to extensions) package won't help that nor benefit other users who don't feel comfortable using the terminal and installing software on the command line or editing shell scripts inside the application package. Of course any contributions/new insights from Python experts are welcome and best placed in the comments of the bug report ;)~suv wrote:I didn't.lewyssmith wrote:Thanks again for pointing to getting Inkscape working for us.
Please try to be patient a little longer and wait for a new Inkscape package for Snow Leopard to be released - the development of the next version 0.48 has entered frost phase and bug hunt will follow soon, hopefully providing more resources to fix Inkscape python extensions on Snow Leopard!