Comment 2 for bug 448285

>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 don't have access to OS X right now, so I'm not sure. System-wide, one might query from Python:
$ python
Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import lxml
>>> print lxml.__path__
['/usr/lib/python2.6/dist-packages/lxml']

So in theory you could write a dummy extension that writes that info to stderr.

> 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).

Agreed. The win32 build should include a module that will at least be *close* to the same version as linux/OS X users. And since the win32 installer (and OSX too?) is bundling lxml, it would make sense to check the lxml version at each Inkscape release IMO.

> - linux: how are the dependencies handled on linux platforms / different distributions?

I think it's a simple flag in the package:
aptitude why python-lxml
i inkscape Recommends python-lxml

> - win32: package includes its own python binary (AFAIK 2.5) as well as lxml and numpy

Yes - 2.5