lxml version bundled with Inkscape is old
Bug #448285 reported by
Chris Mohler
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape Devlibs |
Fix Released
|
Medium
|
Krzysztof Kosinski |
Bug Description
The version of lxml bundled with Inkscape is pretty dated (version 1.3b 2007). Current version is 2.2.2 and adds functionality as well as numerous bug fixes.
This leads to difficulties when writing extensions: for example I was writing an extension on linux that worked fine, but would not work on Windows.
Deleting the bundled lxml and downloading this file:
http://
and extracting into $PROG\python\
tags: | added: extensions-plugins python |
tags: | added: packaging |
affects: | inkscape → inkscape-devlibs |
Changed in inkscape-devlibs: | |
assignee: | nobody → Krzysztof Kosinski (tweenk) |
status: | Confirmed → In Progress |
Changed in inkscape-devlibs: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The OS X packages include lxml for 4 python (intel) versions (2.3, 2.4, 2.5, 2.6) and 3 python (ppc) versions (2.3, 2.4, 2.5). It looks like 4 or more different lxml versions as well (no lxml-*.egg-info included). Do you know how I could easily verify the bundled lxml versions (as a python ignoramus ;-)?
I think it is important to agree on a min version for Python and the included modules on all platforms (there were brief discussions about python versions in bug #387946 and bug #387446).
- linux: how are the dependencies handled on linux platforms / different distributions?
- win32: package includes its own python binary (AFAIK 2.5) as well as lxml and numpy
- osx: there's a dependency to the system-installed python version, lxml and numpy are bundled