On 25/11/09 13:55, ~suv 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)? on OS X snow leopard the items under extensions still give the python error "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 know it's known of, just wondering if a solution was n the horizon. I did try installing python but guess I don't know what I'm doing as it didn't work LOL
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...
No, it's not 'as simple as'. a) There are no installation packages available for both needed modules (lxml and numpy) that allow easy installation without the use of command line tools (if I am mistaken and they exist - please let us know ;-). b) even if the user somehow manages to install both modules as site-packages to Apple's Python, to MacPython or via MacPorts to a yet another python installation, he then has to edit a shell script (setting the path to the python binary he intends to use and the path to the 'site-packages' folder where the new modules have been installed) and/or remove the python files inside the installed Inkscape.app.
The idea of the included python modules in the application package is exactly to avoid this. Most OS X users never need to use the command line and don't expect this to be necessary to use a software like Inkscape.
Of course it is almost 'as simple as' for users who are comfortable working with command line tools and have some python knowledge - there have been several successful workarounds reported. But this certainly contradicts the idea of providing pre-compiled self-contained packages for Inkscape for OS X that don't need a package installer but can be dropped into any folder and launched on double-click.
And IMHO inkscape.org does not have the resources to provide user support for the python module installations. X11 on OS X by itself is already demanding a lot of the bug tracker and support resources on Launchpad.
oops - sh.., sorry, clicked the wrong button - wanted to delete it...
~suv (yet again, embarrassed)