Mailman 3 January 2006 - lxml - The Python XML Toolkit

[lxml-dev] install problem on Windows XP
by Werner F. Bruhin Feb. 2, 2006

Feb. 2, 2006

I am running into problems trying to: \python24\python setup.py install I changed the following in setup.py: #include_dirs = guess_dirs('--cflags', '-I') #library_dirs = guess_dirs('--libs', '-L') # if you want to configure include and library dir manually, you can do # so here, for instance: include_dirs = [r'C:\Python24\Lib\site-packages\libxslt-1.1.14.win32\include',] # '/home/faassen/tmp/local_new/include'] library_dirs = [r'C:\Python24\Lib\site-packages\libxml2-2.6.20.win32\lib'] But I am getting an error that I need .net SDK (error: The .NET Framework SDK needs to be installed before building extensions f or Python.). Did I not change the setup.py correctly or do I really need the .net SDK. Any chance that there is a binary build for Windows XP is available? See you Werner

3 2

[lxml-dev] pretty-print and declaration stripping patch update
by Patrick Wagstrom Jan. 31, 2006

Jan. 31, 2006

Folks, I've updated the pretty-print and declaration stripping patches for the most recent code base. Along the way I realized that due to the new way of writing out the XML, calling _stripDeclaration was not necessary in write (in etree.py). I've fixed the code so it now can output an xml declaration with the document. Syntax is the same as the last series of posts. Thanks! --Patrick

2 1

[lxml-dev] lxml and namespaces
by Andreas Pakulat Jan. 31, 2006

Jan. 31, 2006

Hi, I tried the namespace feature of lxml and there is one thing that bothers me: Creating a new element via Element("{myns}elem1") adds a ns-declaration to it, which is correct and just fine. However when I append this new element to an existing one, which also has a namespace declaration (say elem2), the ns-declaration of my first element persists. I think this is unecessary and confusing if you read the string value of an xml document. If I create new Elements without a parent element to put them into the tree later at various positions I end up with a ton of ns-declarations all declaring the same namespace. So is there a way I'm overlooking to tell lxml: When I append elem1 to elem2, please go through all parent elemens to check for a namespace declaration matching the on of elem1. If you find one, drop the ns declaration from elem1 itself. Now I don't know wether the problem here is actually lxml or libxml2 itself, but I figured I start here and work my way through. Andreas -- You will be attacked by a beast who has the body of a wolf, the tail of a lion, and the face of Donald Duck.

2 5

[lxml-dev] lxml branch
by Godefroid Chapelle Jan. 24, 2006

Jan. 24, 2006

Hi Martijn, list I have checked code in a branch that allow to use a different parser than the default globally shared. This allows to setup different options than the default. All previous tests (321 ?) do pass. I'd be pleased to get feedback about the code before working on the supplementary tests needed. I am not totally sure I went the right way even if it works for me... Cheers -- Godefroid Chapelle (aka __gotcha)- BubbleNet http://bubblenet.be

4 17

Re: [lxml-dev] Re: Namespace API for extension functions
by Stefan Behnel Jan. 23, 2006

Jan. 23, 2006

Paul Everitt wrote: > On Jan 22, 2006, at 5:48 PM, Stefan Behnel wrote: >> Note also that lxml now uses setuptools >> if available. I tried building with and without setuptools and couldn't >> reproduce it now. > > I haven't used setuptools before...do I just install the egg file in scoder2/dist? Sounds like you just used setuptools... :) Still, if it didn't compile, I'd wonder why there should be an .egg file in dist. Have you tried "python setup.py bdist_egg" ? Then, this should work: easy_install dist/lxml_XXXXXXXX.egg See http://peak.telecommunity.com/DevCenter/EasyInstall#downloading-and-install… Regarding the problem, I found this in my site-packages directory: ----------- def swig_sources (self, sources, extension=None): .../python2.4/site-packages/Pyrex/Distutils/build_ext.py def swig_sources(self, sources, *otherargs): sources = _build_ext.swig_sources(self, sources) or sources return _du_build_ext.swig_sources(self, sources, *otherargs) .../python2.4/site-packages/setuptools-0.6a9-py2.4.egg/setuptools/command/build_ext.py ----------- So it's definitely related to setuptools and Pyrex. However, as I said, it runs here, so I can't quite figure out what went wrong there... Stefan

2 1

[lxml-dev] Doctest for Namespace class
by Stefan Behnel Jan. 22, 2006

Jan. 22, 2006

Hi! The Namespace class now has a doctest in scoder2/doc/namespace_extensions.txt. I also gave a quick example on how to use XPath extension functions, but I still somewhat feel that the prefixes should not have to be specified on evaluation. My current example looks like this: .>>> from lxml.etree import Namespace .>>> def tag_of(context, elem): ... return elem[0].tag .>>> namespace = Namespace('myfunctions') .>>> namespace['tagname'] = tag_of .>>> element = XML('<test><honk honking="true"/></test>') .>>> element.xpath('f:tagname(//honk)', {'f' : 'myfunctions'}) 'honk' What bothers me is the {'f' : 'myfunctions'} in there. The user shouldn't have to care about that. What about supporting this: .>>> element.xpath('{myfunctions}tagname(//honk)') My XPath class already supports that for elements, but it is not currently done for extension functions (and not in the two original evaluators either, for backward compatibility). Personally, I'd prefer removing the current extension support completely, since it makes the code rather complicated. Providing two different APIs to the user and then merging the functions from both of them internally is not exactly elegant. Stefan

4 7

[lxml-dev] creating an interface for processing instructions
by Patrick Wagstrom Jan. 20, 2006

Jan. 20, 2006

Hi folks, I'm developing a web app that can rely on the browser to automatically transform XML documents using XSLT. Typically, this is done by inserting an XML processing instruction into the document. However, this introduces a slight wrinkle in the structure of lxml (and elementTree too). Basically, if I understand the code correctly, the ElementTree class has a root node that can be accessed through the getRoot method. However, once I have this node, there is no way to go the next sibling node, at least not that I can see. Normally, this is fine as typical XML documents only have a single root. However, when you include PIs, they actually end up having multiple roots. For example, this is a valid XML document <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="/resources/xslt/blog.xsl"?> <doc> <foo>fadsfad</foo> </doc> Normally, with libxml2 you create a document, add in the node that represents "doc", then add in the PI using addPrevSibling or something like that. When reading in the document, you'll need need to use the next() function get over the PI. However, it doesn't appear there is a way to do this in lxml or in elementTree right now. I've managed to get the PI factory working, I just can't create multi-rooted documents without a whole lot of mangling that would break 100% elementTree compatibility -- because as near as I can tell, elementTree in python subversion can't do this either (or I haven't figured out how to). It can create PIs, but not put them right at the beginning of the document before the root not. Any help on this one? --Patrick

1 0

[lxml-dev] libxml2 2.6.23 and lxml I/O support
by Stefan Behnel Jan. 20, 2006

Jan. 20, 2006

Hi! Version 2.6.23 of libxml2 is out since the early this month and it contains a number of patches, including Geert's long awaited SaveToBuffer patch. So, maybe we should reconsider the I/O patches for lxml? Geert, anything new from the front? Ready to get your stuff accepted? What/where is your current patch? Stefan

3 2

[lxml-dev] XPathModel
by Stefan Behnel Jan. 10, 2006

Jan. 10, 2006

Hi! I had mentioned something about my XPath model a while ago and there was some interest. I now uploaded the project that I wrote it for to Berlios, so the module is now available here: http://svn.berlios.de/wsvn/slow/trunk/src/slow/model/xpathmodel.py?op=file&… It (obviously) uses the namespace extension mechanism that I wrote for lxml. The implementation is basically a metaclass that allows you to write XPath expressions into the body of a Python class and then transforms them at class creation time into getter and setter methods or properties (if possible). It's pretty sophisticated: it supports XPath variables as method arguments, filters for simple XPath result conversion and on-the-fly construction of XML elements. It's even more home grown by need, so it may be a bit difficult to understand at first sight. The package of that module contains a number of other modules that use the XPathModel class to implement various kinds of data class APIs, they may be a good starting point. Hope you like it, Stefan

1 0

[lxml-dev] Re: lxml-dev Digest, Vol 16, Issue 2
by Eric Ferrante Jan. 7, 2006

Jan. 7, 2006

Selon lxml-dev-request(a)codespeak.net: > Send lxml-dev mailing list submissions to > lxml-dev(a)codespeak.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://codespeak.net/mailman/listinfo/lxml-dev > or, via email, send a message with subject or body 'help' to > lxml-dev-request(a)codespeak.net > > You can reach the person managing the list at > lxml-dev-owner(a)codespeak.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lxml-dev digest..." > > > Today's Topics: > > 1. Re: install error (Stefan Behnel) > 2. Re: install error (Olivier Grisel) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 06 Jan 2006 12:21:58 +0100 > From: Stefan Behnel <behnel_ml(a)gkec.informatik.tu-darmstadt.de> > Subject: Re: [lxml-dev] install error > To: Eric Ferrante <ferrante(a)univ-tlse2.fr> > Cc: lxml-dev(a)codespeak.net > Message-ID: <43BE52D6.50404(a)gkec.informatik.tu-darmstadt.de> > Content-Type: text/plain; charset=ISO-8859-1 > > > Eric Ferrante wrote: > > I try to install lxml-0.8, but I get errors with the gcc 4.0. I know the > > problems with gcc 4.0 and I have installed de patches for Pyrex. But I > > get still 6 errors. > > > > My system is the last version of fedora. > > That is a known bug in Pyrex. The patches have been available for months, but > have not yet found their way into all distributions. > > Please use the SVN version of lxml, it now contains the generated C-file. You > therefore no longer have to use Pyrex. > > Stefan > > > ------------------------------ > > Message: 2 > Date: Fri, 06 Jan 2006 14:01:55 +0100 > From: Olivier Grisel <ogrisel(a)nuxeo.com> > Subject: [lxml-dev] Re: install error > To: lxml-dev(a)codespeak.net > Message-ID: <dplpo1$5ds$1(a)sea.gmane.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Stefan Behnel a écrit : > > Eric Ferrante wrote: > >> I try to install lxml-0.8, but I get errors with the gcc 4.0. I know the > >> problems with gcc 4.0 and I have installed de patches for Pyrex. But I > >> get still 6 errors. > >> > >> My system is the last version of fedora. > > > > That is a known bug in Pyrex. The patches have been available for months, > but > > have not yet found their way into all distributions. > > > > Please use the SVN version of lxml, it now contains the generated C-file. > You > > therefore no longer have to use Pyrex. > > Or you can try with this prepatched version of Pyrex that works for me: > > http://svn.nuxeo.org/trac/pub/browser/vendor/Pyrex/tags/0.9.3-gcc4-patched/ > > -- > Olivier > > > > ------------------------------ > > _______________________________________________ > lxml-dev mailing list > lxml-dev(a)codespeak.net > http://codespeak.net/mailman/listinfo/lxml-dev > > > End of lxml-dev Digest, Vol 16, Issue 2 > *************************************** > Thank you. I've tried the first solution, and it seems to be good. I'll be sure when I'll be able to run the product whitch needs lxml. Soon. Thank you one more. Bye. Eric Ferrante ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0