Use lxml-library in a plugin

I have a python script running on a python installation with lxml. How could I import the lxml to use it in a xbmc plugin?

Thanks

Please help me with this. I'm getting crazy...

Thanks

elementtree uses the same syntax and will be a billion times easier to distribute.

If you don't want to use elementtree... you'll have to distribute and install setuptools in your addon for all three, see http://pypi.python.org/pypi/setuptools for how to install in xbmc's python, then easy_install lxml to xbmc's python. It will also require users to already have libxslt & whatever other prerequisites lxml has installed.

Basically, use elementtree instead.

Yes, same advice than rwparris2, give a try to ET, it is a very lib and you just need to provide it with your script. I gave you an example on how to use it on your previous post when you were asking which XML parser were available.

@kimx
One solution is to include the package source as part as your plugin and then add the path with code like:


and then you can use an import statement.

See some of the plugins plugins in my signature, they include things like BeautifulSoup or simpljason. An alternative is to use xml.dom to parse XMLs, see XBMC Xbox Trac Changelog or XBMC Zone Installer.

Thank you for the answers, but the problem is not how to import, but which files I need to import the lib. In my script I use the etree element from lxml. In a normal python install I use this statement to import it:
How could I get the same result in xbmc and which files are needed?
Thanks in advance

You could download the source for lxml (http://pypi.python.org/pypi/lxml/) and pick the contents of the src folder, but somehow I have a feeling they won't work without compiling them for a particular platform... I would try to rewrite the logic you have using the other suggested alternatives...

yes it wont work without compiling. It's depends Os and Python version also. For exmple if you use lxml with your XBMC plugin you should add lxml for all platforms separately (Linux,win32,Os X) and python version must be 2.4. This is huge for 1 plugin. Its approximately 6mb

One more thing, for example you have windows and your python version 2.6 and you developing plugins in this computer. You need lxml for windows and python version for 2.6 but when you release plugin you need lxml for all platforms and for python 2.4.

I'd say - it would make sense to create a Trac request to include the appropriate lxml with Python with XBMC, but given that XBMC Team is concentrated on other tasks now, I don't see that happening soon. While there are other libraries already available with XBMC Python (xml.dom) or out there that could to the same task, the only reason I would against re-writing away from lxml is what, convenience?!

I think this is the easiest way to do it. http://trac.xbmc.org/ticket/7246