Inkscape 0.47 pre 4, OS X 10.6.1, The fantastic lxml wrapper for libxml2
Hello,
I'm testing the latest 0.47 pre4 on OS X - 10.5.8 at work and perspective works just fine. But at home i have OS X - 10.6.1 and doing perspective fails and gives this 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 --------------------------
Is something just not finished in the 0.47 or is it something changed in Snow Leopard?
Regards :)
On Mon, Oct 19, 2009 at 1:45 PM, Jmx <jompx@...36...> wrote:
Hello,
I'm testing the latest 0.47 pre4 on OS X - 10.5.8 at work and perspective works just fine. But at home i have OS X - 10.6.1 and doing perspective fails and gives this 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
Is something just not finished in the 0.47 or is it something changed in Snow Leopard?
See these possibly related bugs/issues: https://bugs.launchpad.net/inkscape/+bug/448285 https://bugs.launchpad.net/inkscape/+bug/321346
I know the team is pushing for a release, but updating the libraries (and verifying that they will be picked up correctly) that are bundled w/the win32 and OS X installers would be a good idea IMO.
Chris
On 19/10/09 20:58, Chris Mohler wrote:
I'm testing the latest 0.47 pre4 on OS X - 10.5.8 at work and perspective works just fine. But at home i have OS X - 10.6.1 and doing perspective fails and gives this 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
Is something just not finished in the 0.47 or is it something changed in Snow Leopard?
due to changes in Snow Leopard.
See these possibly related bugs/issues: https://bugs.launchpad.net/inkscape/+bug/448285 https://bugs.launchpad.net/inkscape/+bug/321346
I know the team is pushing for a release, but updating the libraries (and verifying that they will be picked up correctly) that are bundled w/the win32 and OS X installers would be a good idea IMO.
This issue is known and partly described in Bug #421305 “Inkscape does not run on Mac OSX 10.6”: https://bugs.launchpad.net/inkscape/+bug/421305 and mentioned previously on the mailing-lists: http://article.gmane.org/gmane.comp.graphics.inkscape.devel/31586 http://article.gmane.org/gmane.comp.graphics.inkscape.user/12748 http://article.gmane.org/gmane.comp.graphics.inkscape.user/12751
~suv
On Mon, Oct 19, 2009 at 2:18 PM, ~suv <suv-sf@...58...> wrote:
Is something just not finished in the 0.47 or is it something changed in Snow Leopard?
due to changes in Snow Leopard.
This issue is known and partly described in Bug #421305 “Inkscape does not run on Mac OSX 10.6”: https://bugs.launchpad.net/inkscape/+bug/421305 and mentioned
Missed that one - thanks... (still new around here ;)
Chris
On 19/10/09 21:20, Chris Mohler wrote:
On Mon, Oct 19, 2009 at 2:18 PM, ~suv <suv-sf@...58...> wrote:
Is something just not finished in the 0.47 or is it something changed in Snow Leopard?
due to changes in Snow Leopard.
This issue is known and partly described in Bug #421305 “Inkscape does not run on Mac OSX 10.6”: https://bugs.launchpad.net/inkscape/+bug/421305 and mentioned
Missed that one - thanks...
That's because it's hidden in the comments as no Snow Leopard user has filed a separate bug report about it yet - and I'm hesitant to do it because I haven't upgraded and could not test or verify any patches or fixes locally.
(still new around here ;)
I disagree! ;-)
~suv
On 19/10/2009, at 2:18 PM, ~suv wrote:
On 19/10/09 20:58, Chris Mohler wrote:
I'm testing the latest 0.47 pre4 on OS X - 10.5.8 at work and perspective works just fine. But at home i have OS X - 10.6.1 and doing perspective fails and gives this 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
Is something just not finished in the 0.47 or is it something changed in Snow Leopard?
due to changes in Snow Leopard.
See these possibly related bugs/issues: https://bugs.launchpad.net/inkscape/+bug/448285 https://bugs.launchpad.net/inkscape/+bug/321346
I know the team is pushing for a release, but updating the libraries (and verifying that they will be picked up correctly) that are bundled w/the win32 and OS X installers would be a good idea IMO.
This issue is known and partly described in Bug #421305 “Inkscape does not run on Mac OSX 10.6”: https://bugs.launchpad.net/inkscape/+bug/421305 and mentioned previously on the mailing-lists: http://article.gmane.org/gmane.comp.graphics.inkscape.devel/31586 http://article.gmane.org/gmane.comp.graphics.inkscape.user/12748 http://article.gmane.org/gmane.comp.graphics.inkscape.user/12751
I've spent a fair bit of time trying to fix this for Snow Leopard, but I guess it has something to do with 64 vs. 32-bit incompatibilities (though I actually still can't get it to work by forcing Inscape and particularly python to run in 32 bit mode -- possibly the mechanism for doing this does not work properly). At the moment I think we are going to have to have a separate Snow Leopard package with it's own specially built python modules.
I've been busy overseas in Texas for the last week, but will be heading back home tomorrow to Australia and then I'll have time to look at this some more. In the meantime, if someone else wants to follow the process for compiling the python modules from a Snow Leopard machine and then replace the python components in the pre- built app bundle (as ~suv suggested in the "Advice on how to update lxml on OS X" thread), then I think this is the best solution we have right now.
Cheers, Michael
On 20/10/09 05:31, Michael Wybrow wrote:
I've been busy overseas in Texas for the last week, but will be heading back home tomorrow to Australia and then I'll have time to look at this some more. In the meantime, if someone else wants to follow the process for compiling the python modules from a Snow Leopard machine and then replace the python components in the pre-built app bundle (as ~suv suggested in the "Advice on how to update lxml on OS X" thread), then I think this is the best solution we have right now.
quick question: can the MacPorts python modules just be copied from '${prefix}/lib/python2.5/site-packages' or '${prefix}/Library/Frameworks/Python.framework/Versions/Current/lib/python2.6/site-packages' and put into the bundle 'python/site-packages/${arch}' or do they need specific configure options to be 'relocatable'?
~suv
BTW - for any Snow Leopard user willing to try - here is a InkscapeForum thread about a reported successful python module installation on SL, although it remains unclear to me where the modules finally were installed ;-) http://www.inkscapeforum.com/viewtopic.php?f=29&t=3708&start=0&hilit=Snow+Leopard
quick question: can the MacPorts python modules just be copied from '${prefix}/lib/python2.5/site-packages' or '${prefix}/Library/Frameworks/Python.framework/Versions/Current/lib/python2.6/site-packages' and put into the bundle 'python/site-packages/${arch}' or do they need specific configure options to be 'relocatable'?
If I remember well, this is how I did it in the first place. It should just work fine.
JiHO --- http://maururu.net
Hi again,
I have no clue how to update what to get this working. Will this be fixed in the 0.47 final or will all 10.6 users be without the effects?
Cheers :drunk:
On Tue, 2009-11-10 at 04:35 -0800, Jmx wrote:
Hi again,
I have no clue how to update what to get this working. Will this be fixed in the 0.47 final or will all 10.6 users be without the effects?
I think that this is up to whoever ends up packaging 0.47 on OSX and whether or not a solution has been found.
Cheers, Josh
participants (6)
-
Chris Mohler -
JiHO -
Jmx -
Joshua A. Andler -
Michael Wybrow -
~suv