http://permalink.gmane.org/gmane.comp.python.lxml.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.python.lxml.devel/4081 Hi, I thought I answer your mail when I really used it and today it is completed ;) Pyxer now offers a small template language that is quite similar to Genshi but works on Google App Engine. The CSSSelector routine makes accessing certain parts of the document much easer. Thanks a lot for this useful peace of code! Download: http://pypi.python.org/pypi/pyxer/0.6.0 BTW: Ian, my work started with your great tutorial "Another Do-It-Yourself Framework", that was a little treasure of ideas ;) http://pythonpaste.org/webob/do-it-yourself.html Dirk Ian Bicking schrieb: Dirk Holtwick 2008-10-05T14:22:33 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4080 Hi, Max Ivanov wrote: That's because you get a unicode string as input, which is not compatible with a char*. This is actually very inefficient. Cython will generate code here that retrieves the char* from the Python input string and then creates a new Python string from it to pass it into the .append() method. lxml uses a C interface internally, but AFAIR, it's not exposed at the C API level. Check the sources in parser.pxi and parsertarget.pxi. Stefan Stefan Behnel 2008-10-02T19:26:48 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4079 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev Hanni Ali 2008-10-02T14:11:17 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4078 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev Hanni Ali 2008-10-02T14:10:05 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4077 Haven't looked at that yet. I'm pretty confident though that we need libxml2 to be compiled for x64 first. I use the binaries provided by Igor Zlatkovic (http://www.zlatkovic.com/libxml.en.html) to build lxml. Maybe you can get the ball rolling by pinging Igor about providing x64 binaries? I'm a little bit short of time to start that discussion, but will eventually need a x64 build myself, for using lxml with IIS in Windows Server x64. On Thu, Oct 2, 2008 at 10:56 AM, Hanni Ali <hanni.ali< at >gmail.com> wrote: Sidnei da Silva 2008-10-02T14:06:40 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4076 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev Hanni Ali 2008-10-02T13:56:53 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4075 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev jholg< at >gmx.de 2008-10-02T06:49:23 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4074 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev Terrence Brannon 2008-10-02T00:45:18 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4073 Just a random guess, but FC5 is pretty ancient as linux distributions go. You might have better luck trying a version of lxml that's as old as your distro, like 1.0.x or so. If you're lucky, maybe 1.3.6 will work. If you want to be insistent about getting 2.1.2 built, I wouldn't be surprised if you'll need to build an updated gcc and libc to be able to build it. Upgrading your OS would be easier. John Krukoff 2008-09-30T21:59:54 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4072 Hi all, I've just installed the latest lxml and tried to compile it (first I had to get the latest libxml2 and libxslt), it crashes on the first file lxml.etree.c with a "internal compiler error". I'm on a Linux box running Fedora 5, with python 2.4.2. Should I report this as a bug somewhere else ? Any suggestions on how to work around this ? maybe a problem with version compatibility, between lxml and python ? or libxml2, libxslt ? this is my very first attempt at installing anything written in python, please forgive my ignorance. Detailed trace below. Thanks for helping, Joao --------------------- [joao< at >fox lxml-2.1.2]$ python setup.py build Building lxml version 2.1.2. NOTE: Trying to build without Cython, pre-generated 'src/lxml/lxml.etree.c' needs to be available. Using build configuration of libxslt 1.1.24 Building against libxml2/libxslt in one of the following directories: /w7/u/libxslt-1.1.24/lib /w7/u/libxml2-2.7.1/lib running build running build_py running build_ext building 'lxml.e Joao Moreira 2008-09-30T21:37:58 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4071 Hi all! I'm trying to write TargetParser in Cython just to compare perfomance. The problem is with data types. If I define data method as "def data(self, char *data):" I'm unable to use it as TargetParser. I get " def data(self, char *data): UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-4: ordinal not in range(128)" error. I could instance and directly call data() and close() methods and everything works fine, but it refuses to work with lxml. Small testcase following: ----- _target.pyx ----------- cdef class Target: cdef list _data def __init__(self): self._data = [] def data(self, char *data): self._data.append(data) def close(self): return ''.join(self._data) ---- end of target.pyx ------ ---- test.py ------- # -*- encoding: utf-8 -*- import lxml.html from lxml import etree from _target import Target res = etree.HTML(u"<span>ABCD</span>", parser=lxml.html.HTMLParser(target = Target())) -------end of target.pyx ------ Max Ivanov 2008-09-29T14:56:41 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4070 Hallo list I've hit a snag with lxml and a DOCTYPE decleration. I don't know if I'm to blame here, but would appreciate help either way. I've tried this with an old (1.3.2) and newer (2.0.6) lxml version. (this example is roughly based on the code at http://codespeak.net/lxml/tutorial.html) from lxml import etree from StringIO import StringIO tree = etree.parse(StringIO("""<!DOCTYPE TS><TS></TS>""")) tree.docinfo.doctype '' in the wild in Qt .ts files). My real issue is round-trip problems in a reading-writing cycle where the DOCTYPE is lost, but I guess not being able to use .docinfo.doctype is already a problem. Any help will be appreciated. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/vrot-mango _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev F Wolff 2008-09-29T10:49:15 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4069 So, I was trying to figure out what happend to my meta tags when using the lxml.html module, and saw the note in the documentation that html.tostring will handle them as so: However, that doesn't seem to actually be the case. It looks like etree.tostring is never creating the meta tag as html.tostring appears to expect, and instead the include_meta_content_type flag is simply controlling whether any found meta tag is removed from the output (with an re!). Python 2.5.2 (r252:60911, Sep 22 2008, 12:08:38) [GCC 4.1.2 (Gentoo 4.1.2 p1.1)] on linux2 Type "help", "copyright", "credits" or "license" for more information. True ) '<p>&#169;2008</p>' Not present there, so I figure maybe it's because it's not being treated as a complete document? True ) '<html><body><p>&#169;2008</p></body></html>' Parsing as document doesn't create it either. = True ) '<html><body><p>\xa92008</p></body></html>' Okay, maybe it's because I'm using the default encoding for HTML (us-ascii)? Nope, trying something else doesn't cau John Krukoff 2008-09-25T23:33:11 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4068 After some abortive fumbling until I figured out I needed to have cython installed to use the patch, I gave it a try. Looks like it works fine here for my use case: <Element html at 81b471c> = 'us-ascii' ) ) <Element html at 81b444c> John Krukoff 2008-09-25T23:32:38 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4067 FWIW, utf-8 does work. Here's some that I tried, and that worked for me: utf8 utf16 iso-8859-1 through iso-8859-9 shift_jis Just mentioning, since you said that utf8 doesn't work (I would have noticed that a long time ago). Anyway, I'll give the patch a try. Thanks for your always quick response! John Krukoff 2008-09-17T20:14:28 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4066 Stefan Behnel wrote: ... not a complete one, though. It doesn't work for iterparse(). I'll have to look into that. Stefan Stefan Behnel 2008-09-17T19:56:26 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4065 Hi, John Krukoff wrote: No, you've found a bug. The way the override input encoding is checked by the parser instantiation is simply wrong, it doesn't find any "standard" encoding (utf-8 or ASCII), neither does it find iconv encodings. Here's a fix. Stefan _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev Stefan Behnel 2008-09-17T19:31:58 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4064 So, I've been trying to deal with some places where I need to force the parser's encoding, and I've been surprised by how little it seems to support. Specifically, 'ascii' isn't a supported encoding: Python 2.5.2 (r252:60911, Jul 31 2008, 15:38:58) [GCC 4.1.2 (Gentoo 4.1.2 p1.1)] on linux2 Type "help", "copyright", "credits" or "license" for more information. Traceback (most recent call last): File "<stdin>", line 1, in <module> File "parser.pxi", line 1240, in lxml.etree.XMLParser.__init__ (src/lxml/lxml.etree.c:58722) File "parser.pxi", line 711, in lxml.etree._BaseParser.__init__ (src/lxml/lxml.etree.c:55050) LookupError: unknown encoding: 'ascii' u'2.1.1' I checked the libxml2 documentation, and that claims that on linux it supports all the encodings that iconv does, which is quite a lot. Almost none of those returned by iconv actually work, though. Am I doing something wrong here by trying to specify the encoding in this way? Is there something weird about my build? If everything is working a John Krukoff 2008-09-17T19:08:43 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4063 Hi, I never used SunOS or tried to build lxml on it, but ... Owen Zhang wrote: This looks like there is something wrong on your system. Have you looked into the /usr/include/sys/siginfo.h file to see what the compiler is complaining about in the above lines? Where is the ctid_t type defined on your system? Stefan Stefan Behnel 2008-09-17T17:21:33 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4062 Hi, Steven Vereecken wrote: Here's a quick-fix for that problem. Stefan _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev Stefan Behnel 2008-09-17T13:25:04 http://permalink.gmane.org/gmane.comp.python.lxml.devel/4061 Hi, Steven Vereecken wrote: Thanks for the report. These definitely are bugs (also in 2.0 AFAICT). I'll look into them when I find the time. They shouldn't be hard to fix, so you can give it a try yourself. Stefan Stefan Behnel 2008-09-17T12:13:10 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.lxml.devel