Comment 11 for bug 1086296

Still reproduces with
- Inkscape 0.91 r13725 (OS X 10.7.5)
- lp:inkscape/0.92.x r15044 (OS X 10.7.5)
- lp:inkscape r15036 (OS X 10.7.5)
- lp:inkscape r15077 (Ubuntu 14.04.5 LTS)

--
@Beluga - you are unlikely to revisit this report, but anyway: Inkscape's python-based extensions are not yet compatible with Python 3, you need to make sure that Inkscape spawns the Python 2 interpreter (first 'python' binary in $PATH; else patch the source to force it to spawn 'python2' explicitly), and have Python 2, as well as the lxml and numpy modules for Python 2 installed. There's no point though to litter the fact about your local partially broken setup across the bug tracker: if you can't figure it out yourself, ask for help e.g. on irc or on one of the mailing lists, or - if you installed unstable Inkscape trunk via package maintained by your distro (archlinux: inkscape-bzr) - file a report there to properly manage python migration (python2 -> python3) for all packages they offer. IIRC last time I checked, the official arch linux packages for inkscape and inkscape-bzr did ok (patching the source to substitute 'python' with 'python2' for the interpreter, with (optional) dependencies on the python2 modules; though oddly no explicit runtime dependency on python2 itself (?)).