Mailman 3 July 2006 - lxml - The Python XML Toolkit

[lxml-dev] Benchmark results on parse/iterparse
by Stefan Behnel 10 Aug '06

10 Aug '06

Hi all, I extended bench.py to support benchmarks on serialised XML data, so now there are micro-benchmarks for the plain parser performance. I attached some results which are pretty impressive. Expat claims to be the fastest XML parser on earth - and it looks like there's some truth in that statement. cET (1.0.5) beats lxml (trunk and iterparse branch) in virtually every parser benchmark. It's even up to 80% faster for large trees. On the other hand, cET is still much slower for serialisation (up to 30x!), so lxml easily wins the round-trip benchmarks for reading and writing XML and is some 3-4x faster at the end. For the iterparse benchmarks, lxml suffers slightly from its object creation overhead (and maybe also the young implementation), but the overhead is acceptable compared to the overall parse time. As expected, the additional overhead for cET is extremely small here, it's almost as fast as the plain parser. So, for (typical?) iterparse() applications that extract small amounts of data from large XML streams on the fly, cET is pretty much unbeatable. For everything else, lxml is still my favourite. :) Stefan Preparing test suites and trees ... Running benchmark on lxe, cET, ET Setup times for trees in seconds: lxe: -- S- U- -A SA UA T1: 0.1323 0.1295 0.1309 0.1400 0.1294 0.1281 T2: 0.1345 0.1326 0.1324 0.1439 0.1443 0.1436 T3: 0.0358 0.0286 0.0290 0.0872 0.0852 0.0867 T4: 0.0007 0.0006 0.0006 0.0018 0.0018 0.0018 cET: -- S- U- -A SA UA T1: 0.0427 0.0433 0.0421 0.0418 0.0426 0.0425 T2: 0.0440 0.0426 0.0448 0.0496 0.0424 0.0445 T3: 0.0109 0.0102 0.0110 0.0185 0.0146 0.0148 T4: 0.0001 0.0001 0.0001 0.0001 0.0001 0.0001 ET : -- S- U- -A SA UA T1: 0.2288 0.2882 0.2279 0.2701 0.3036 0.2273 T2: 0.2972 0.2352 0.2890 0.3218 0.2337 0.3112 T3: 0.0533 0.0572 0.0534 0.0616 0.0573 0.0949 T4: 0.0009 0.0009 0.0008 0.0008 0.0009 0.0009 lxe: iterparse_stringIO (S-X T1 ) 222.9110 msec/pass, best of ( 227.3209 224.8156 222.9110 ) cET: iterparse_stringIO (S-X T1 ) 38.3651 msec/pass, best of ( 38.6973 38.3651 38.4331 ) ET : iterparse_stringIO (S-X T1 ) 362.5654 msec/pass, best of ( 399.9243 364.9337 362.5654 ) lxe: iterparse_stringIO (SAX T1 ) 223.7216 msec/pass, best of ( 229.2649 225.4670 223.7216 ) cET: iterparse_stringIO (SAX T1 ) 38.7985 msec/pass, best of ( 38.8003 38.7985 39.0118 ) ET : iterparse_stringIO (SAX T1 ) 365.6647 msec/pass, best of ( 365.7858 368.4628 365.6647 ) lxe: iterparse_stringIO (U-X T1 ) 223.2167 msec/pass, best of ( 228.4652 225.6853 223.2167 ) cET: iterparse_stringIO (U-X T1 ) 38.6407 msec/pass, best of ( 38.9079 38.6407 38.7212 ) ET : iterparse_stringIO (U-X T1 ) 361.4145 msec/pass, best of ( 361.5446 362.3198 361.4145 ) lxe: iterparse_stringIO (UAX T1 ) 223.9983 msec/pass, best of ( 230.2715 224.7750 223.9983 ) cET: iterparse_stringIO (UAX T1 ) 38.9739 msec/pass, best of ( 39.1283 38.9739 38.9918 ) ET : iterparse_stringIO (UAX T1 ) 365.9984 msec/pass, best of ( 365.9984 368.7172 367.6013 ) lxe: iterparse_stringIO (S-X T2 ) 232.9033 msec/pass, best of ( 237.3149 233.7498 232.9033 ) cET: iterparse_stringIO (S-X T2 ) 41.1875 msec/pass, best of ( 41.4992 41.2292 41.1875 ) ET : iterparse_stringIO (S-X T2 ) 383.4325 msec/pass, best of ( 383.8255 386.8770 383.4325 ) lxe: iterparse_stringIO (SAX T2 ) 248.6702 msec/pass, best of ( 262.2535 251.9383 248.6702 ) cET: iterparse_stringIO (SAX T2 ) 46.2867 msec/pass, best of ( 46.3457 46.2998 46.2867 ) ET : iterparse_stringIO (SAX T2 ) 406.4786 msec/pass, best of ( 407.3699 406.4786 408.3880 ) lxe: iterparse_stringIO (U-X T2 ) 232.0476 msec/pass, best of ( 239.1271 232.3972 232.0476 ) cET: iterparse_stringIO (U-X T2 ) 41.0636 msec/pass, best of ( 41.0744 41.0636 41.1089 ) ET : iterparse_stringIO (U-X T2 ) 383.7441 msec/pass, best of ( 383.8562 384.8858 383.7441 ) lxe: iterparse_stringIO (UAX T2 ) 250.2190 msec/pass, best of ( 255.8399 250.2190 250.2771 ) cET: iterparse_stringIO (UAX T2 ) 46.3599 msec/pass, best of ( 46.5231 46.3599 47.1866 ) ET : iterparse_stringIO (UAX T2 ) 406.6847 msec/pass, best of ( 410.7563 406.6847 415.3738 ) lxe: iterparse_stringIO (S-X T3 ) 21.0934 msec/pass, best of ( 21.1457 21.0934 21.1917 ) cET: iterparse_stringIO (S-X T3 ) 9.9643 msec/pass, best of ( 9.9643 9.9952 9.9998 ) ET : iterparse_stringIO (S-X T3 ) 119.0730 msec/pass, best of ( 119.0730 119.2219 119.3496 ) lxe: iterparse_stringIO (SAX T3 ) 46.2915 msec/pass, best of ( 51.1358 46.5834 46.2915 ) cET: iterparse_stringIO (SAX T3 ) 41.7721 msec/pass, best of ( 41.7721 43.1893 41.8128 ) ET : iterparse_stringIO (SAX T3 ) 252.5569 msec/pass, best of ( 253.2359 252.5569 257.7912 ) lxe: iterparse_stringIO (U-X T3 ) 21.2006 msec/pass, best of ( 21.6766 21.2006 21.6195 ) cET: iterparse_stringIO (U-X T3 ) 10.1142 msec/pass, best of ( 10.1593 10.1525 10.1142 ) ET : iterparse_stringIO (U-X T3 ) 118.9059 msec/pass, best of ( 119.9316 118.9059 119.0838 ) lxe: iterparse_stringIO (UAX T3 ) 46.0920 msec/pass, best of ( 50.7096 46.3383 46.0920 ) cET: iterparse_stringIO (UAX T3 ) 41.7240 msec/pass, best of ( 41.9300 41.7240 41.9742 ) ET : iterparse_stringIO (UAX T3 ) 253.6689 msec/pass, best of ( 253.6689 253.6885 255.1465 ) lxe: iterparse_stringIO (S-X T4 ) 1.0302 msec/pass, best of ( 1.1030 1.0365 1.0302 ) cET: iterparse_stringIO (S-X T4 ) 0.3072 msec/pass, best of ( 0.3244 0.3115 0.3072 ) ET : iterparse_stringIO (S-X T4 ) 2.8629 msec/pass, best of ( 2.8674 2.8629 2.9106 ) lxe: iterparse_stringIO (SAX T4 ) 1.6899 msec/pass, best of ( 1.6899 1.6941 1.6969 ) cET: iterparse_stringIO (SAX T4 ) 0.9437 msec/pass, best of ( 0.9663 0.9437 0.9659 ) ET : iterparse_stringIO (SAX T4 ) 5.9165 msec/pass, best of ( 5.9764 5.9165 5.9525 ) lxe: iterparse_stringIO (U-X T4 ) 1.0378 msec/pass, best of ( 1.0475 1.0444 1.0378 ) cET: iterparse_stringIO (U-X T4 ) 0.3046 msec/pass, best of ( 0.3141 0.3144 0.3046 ) ET : iterparse_stringIO (U-X T4 ) 2.8697 msec/pass, best of ( 2.8855 2.8799 2.8697 ) lxe: iterparse_stringIO (UAX T4 ) 1.7076 msec/pass, best of ( 1.7076 1.7481 1.7081 ) cET: iterparse_stringIO (UAX T4 ) 0.9469 msec/pass, best of ( 0.9611 0.9520 0.9469 ) ET : iterparse_stringIO (UAX T4 ) 6.0304 msec/pass, best of ( 6.0437 6.0304 6.0345 ) lxe: iterparse_stringIO_clear (S-X T1 ) 234.3113 msec/pass, best of ( 234.3113 246.4326 256.5073 ) cET: iterparse_stringIO_clear (S-X T1 ) 45.1311 msec/pass, best of ( 45.1311 46.6361 45.1353 ) ET : iterparse_stringIO_clear (S-X T1 ) 398.4236 msec/pass, best of ( 411.1450 417.0196 398.4236 ) lxe: iterparse_stringIO_clear (SAX T1 ) 232.9236 msec/pass, best of ( 234.6838 235.7229 232.9236 ) cET: iterparse_stringIO_clear (SAX T1 ) 44.5997 msec/pass, best of ( 44.5997 44.6131 44.6254 ) ET : iterparse_stringIO_clear (SAX T1 ) 391.3037 msec/pass, best of ( 391.3037 392.3368 391.4310 ) lxe: iterparse_stringIO_clear (U-X T1 ) 230.3221 msec/pass, best of ( 240.0502 230.3221 230.4537 ) cET: iterparse_stringIO_clear (U-X T1 ) 44.5020 msec/pass, best of ( 44.5403 44.5163 44.5020 ) ET : iterparse_stringIO_clear (U-X T1 ) 392.5360 msec/pass, best of ( 392.5360 392.7761 392.8283 ) lxe: iterparse_stringIO_clear (UAX T1 ) 232.4709 msec/pass, best of ( 233.1237 232.5471 232.4709 ) cET: iterparse_stringIO_clear (UAX T1 ) 44.6517 msec/pass, best of ( 44.8149 44.6950 44.6517 ) ET : iterparse_stringIO_clear (UAX T1 ) 391.4469 msec/pass, best of ( 393.7384 393.8401 391.4469 ) lxe: iterparse_stringIO_clear (S-X T2 ) 237.8001 msec/pass, best of ( 244.5833 239.2776 237.8001 ) cET: iterparse_stringIO_clear (S-X T2 ) 46.5421 msec/pass, best of ( 46.5820 46.5421 46.6870 ) ET : iterparse_stringIO_clear (S-X T2 ) 404.6504 msec/pass, best of ( 405.8105 404.6504 406.5170 ) lxe: iterparse_stringIO_clear (SAX T2 ) 256.2644 msec/pass, best of ( 256.2644 256.6346 256.5515 ) cET: iterparse_stringIO_clear (SAX T2 ) 51.3243 msec/pass, best of ( 51.4606 51.3311 51.3243 ) ET : iterparse_stringIO_clear (SAX T2 ) 428.6695 msec/pass, best of ( 428.6695 429.9673 429.0031 ) lxe: iterparse_stringIO_clear (U-X T2 ) 238.2270 msec/pass, best of ( 238.2270 238.4732 238.4163 ) cET: iterparse_stringIO_clear (U-X T2 ) 46.8345 msec/pass, best of ( 46.8345 46.9356 47.8009 ) ET : iterparse_stringIO_clear (U-X T2 ) 407.4448 msec/pass, best of ( 407.4448 417.0420 412.9830 ) lxe: iterparse_stringIO_clear (UAX T2 ) 255.1546 msec/pass, best of ( 255.1546 256.3821 258.1754 ) cET: iterparse_stringIO_clear (UAX T2 ) 51.4117 msec/pass, best of ( 51.7307 51.6235 51.4117 ) ET : iterparse_stringIO_clear (UAX T2 ) 427.9256 msec/pass, best of ( 428.1150 435.2808 427.9256 ) lxe: iterparse_stringIO_clear (S-X T3 ) 24.3242 msec/pass, best of ( 24.3841 24.3453 24.3242 ) cET: iterparse_stringIO_clear (S-X T3 ) 11.3448 msec/pass, best of ( 11.5487 11.3886 11.3448 ) ET : iterparse_stringIO_clear (S-X T3 ) 127.7567 msec/pass, best of ( 128.1610 127.7567 128.4989 ) lxe: iterparse_stringIO_clear (SAX T3 ) 53.2374 msec/pass, best of ( 53.4208 53.2374 53.7359 ) cET: iterparse_stringIO_clear (SAX T3 ) 38.3572 msec/pass, best of ( 38.4457 38.3572 38.3621 ) ET : iterparse_stringIO_clear (SAX T3 ) 254.7633 msec/pass, best of ( 257.4664 254.7633 255.7398 ) lxe: iterparse_stringIO_clear (U-X T3 ) 24.6667 msec/pass, best of ( 24.7798 24.6667 24.7138 ) cET: iterparse_stringIO_clear (U-X T3 ) 11.3932 msec/pass, best of ( 11.5611 11.3932 11.5425 ) ET : iterparse_stringIO_clear (U-X T3 ) 127.7254 msec/pass, best of ( 127.8360 127.9421 127.7254 ) lxe: iterparse_stringIO_clear (UAX T3 ) 52.9185 msec/pass, best of ( 52.9185 53.2012 52.9428 ) cET: iterparse_stringIO_clear (UAX T3 ) 38.2394 msec/pass, best of ( 38.4341 38.2394 38.3053 ) ET : iterparse_stringIO_clear (UAX T3 ) 253.7129 msec/pass, best of ( 254.9093 254.8415 253.7129 ) lxe: iterparse_stringIO_clear (S-X T4 ) 1.1246 msec/pass, best of ( 1.2300 1.1246 1.1279 ) cET: iterparse_stringIO_clear (S-X T4 ) 0.3431 msec/pass, best of ( 0.3467 0.3463 0.3431 ) ET : iterparse_stringIO_clear (S-X T4 ) 3.0261 msec/pass, best of ( 3.0261 3.0825 3.0340 ) lxe: iterparse_stringIO_clear (SAX T4 ) 1.8222 msec/pass, best of ( 1.8494 1.8222 1.8429 ) cET: iterparse_stringIO_clear (SAX T4 ) 0.9881 msec/pass, best of ( 0.9933 0.9881 1.0033 ) ET : iterparse_stringIO_clear (SAX T4 ) 6.1015 msec/pass, best of ( 6.1317 6.1015 6.1112 ) lxe: iterparse_stringIO_clear (U-X T4 ) 1.1314 msec/pass, best of ( 1.1320 1.1569 1.1314 ) cET: iterparse_stringIO_clear (U-X T4 ) 0.3512 msec/pass, best of ( 0.3577 0.3564 0.3512 ) ET : iterparse_stringIO_clear (U-X T4 ) 3.0102 msec/pass, best of ( 3.0351 3.0412 3.0102 ) lxe: iterparse_stringIO_clear (UAX T4 ) 1.8182 msec/pass, best of ( 1.8478 1.8182 1.8598 ) cET: iterparse_stringIO_clear (UAX T4 ) 0.9898 msec/pass, best of ( 0.9898 0.9990 0.9943 ) ET : iterparse_stringIO_clear (UAX T4 ) 6.1685 msec/pass, best of ( 6.2379 6.2236 6.1685 ) lxe: parse_stringIO (S-X T1 ) 170.6294 msec/pass, best of ( 173.7078 175.0854 170.6294 ) cET: parse_stringIO (S-X T1 ) 31.2479 msec/pass, best of ( 31.4530 31.2479 31.2610 ) ET : parse_stringIO (S-X T1 ) 320.9497 msec/pass, best of ( 321.8702 322.3815 320.9497 ) lxe: parse_stringIO (SAX T1 ) 171.2800 msec/pass, best of ( 171.2800 175.6441 173.7187 ) cET: parse_stringIO (SAX T1 ) 31.3205 msec/pass, best of ( 32.3134 31.3205 31.3392 ) ET : parse_stringIO (SAX T1 ) 323.7324 msec/pass, best of ( 323.7324 323.7890 328.4510 ) lxe: parse_stringIO (U-X T1 ) 171.6893 msec/pass, best of ( 172.5678 174.2148 171.6893 ) cET: parse_stringIO (U-X T1 ) 31.2387 msec/pass, best of ( 32.1226 31.2387 31.4539 ) ET : parse_stringIO (U-X T1 ) 321.3753 msec/pass, best of ( 323.4447 321.7778 321.3753 ) lxe: parse_stringIO (UAX T1 ) 171.9517 msec/pass, best of ( 171.9517 174.0736 176.9163 ) cET: parse_stringIO (UAX T1 ) 31.5030 msec/pass, best of ( 34.8593 31.5832 31.5030 ) ET : parse_stringIO (UAX T1 ) 323.3877 msec/pass, best of ( 323.6831 323.3877 329.6061 ) lxe: parse_stringIO (S-X T2 ) 179.9828 msec/pass, best of ( 179.9828 181.4266 182.8689 ) cET: parse_stringIO (S-X T2 ) 33.5708 msec/pass, best of ( 34.6295 33.6188 33.5708 ) ET : parse_stringIO (S-X T2 ) 340.2606 msec/pass, best of ( 340.2606 340.5859 342.8782 ) lxe: parse_stringIO (SAX T2 ) 197.7678 msec/pass, best of ( 197.7678 199.4126 199.2439 ) cET: parse_stringIO (SAX T2 ) 38.9390 msec/pass, best of ( 40.0341 38.9390 39.0063 ) ET : parse_stringIO (SAX T2 ) 364.3468 msec/pass, best of ( 365.5197 364.3468 365.6537 ) lxe: parse_stringIO (U-X T2 ) 182.7992 msec/pass, best of ( 182.9719 182.9173 182.7992 ) cET: parse_stringIO (U-X T2 ) 33.7937 msec/pass, best of ( 34.7863 33.8375 33.7937 ) ET : parse_stringIO (U-X T2 ) 340.1892 msec/pass, best of ( 340.1892 341.4799 342.9891 ) lxe: parse_stringIO (UAX T2 ) 197.9534 msec/pass, best of ( 197.9534 199.2566 206.4527 ) cET: parse_stringIO (UAX T2 ) 38.9602 msec/pass, best of ( 40.2117 38.9602 39.0238 ) ET : parse_stringIO (UAX T2 ) 365.2490 msec/pass, best of ( 366.4139 366.0356 365.2490 ) lxe: parse_stringIO (S-X T3 ) 9.3905 msec/pass, best of ( 9.4029 9.3905 9.4458 ) cET: parse_stringIO (S-X T3 ) 7.6507 msec/pass, best of ( 7.6840 7.6507 7.7423 ) ET : parse_stringIO (S-X T3 ) 108.2791 msec/pass, best of ( 108.2791 110.4766 108.3301 ) lxe: parse_stringIO (SAX T3 ) 48.6069 msec/pass, best of ( 48.6069 48.8698 48.9391 ) cET: parse_stringIO (SAX T3 ) 39.8525 msec/pass, best of ( 40.9317 39.8525 39.9056 ) ET : parse_stringIO (SAX T3 ) 237.2957 msec/pass, best of ( 237.5886 237.2957 237.4677 ) lxe: parse_stringIO (U-X T3 ) 9.3709 msec/pass, best of ( 9.4539 9.3835 9.3709 ) cET: parse_stringIO (U-X T3 ) 7.5603 msec/pass, best of ( 7.7213 7.6098 7.5603 ) ET : parse_stringIO (U-X T3 ) 108.1631 msec/pass, best of ( 108.1631 108.8036 108.1696 ) lxe: parse_stringIO (UAX T3 ) 48.6735 msec/pass, best of ( 48.6735 48.8036 48.9602 ) cET: parse_stringIO (UAX T3 ) 39.7455 msec/pass, best of ( 40.0213 39.8740 39.7455 ) ET : parse_stringIO (UAX T3 ) 237.9971 msec/pass, best of ( 237.9971 238.7502 238.3795 ) lxe: parse_stringIO (S-X T4 ) 0.3790 msec/pass, best of ( 0.4000 0.3790 0.3791 ) cET: parse_stringIO (S-X T4 ) 0.2547 msec/pass, best of ( 0.2676 0.2568 0.2547 ) ET : parse_stringIO (S-X T4 ) 2.5935 msec/pass, best of ( 2.5935 2.5990 2.5970 ) lxe: parse_stringIO (SAX T4 ) 1.1852 msec/pass, best of ( 1.2173 1.1852 1.2512 ) cET: parse_stringIO (SAX T4 ) 0.8995 msec/pass, best of ( 0.9106 0.8995 0.9005 ) ET : parse_stringIO (SAX T4 ) 5.5938 msec/pass, best of ( 5.6073 5.6163 5.5938 ) lxe: parse_stringIO (U-X T4 ) 0.3752 msec/pass, best of ( 0.3799 0.3844 0.3752 ) cET: parse_stringIO (U-X T4 ) 0.2558 msec/pass, best of ( 0.2732 0.2599 0.2558 ) ET : parse_stringIO (U-X T4 ) 2.5950 msec/pass, best of ( 2.6326 2.6283 2.5950 ) lxe: parse_stringIO (UAX T4 ) 1.1881 msec/pass, best of ( 1.1881 1.2204 1.2204 ) cET: parse_stringIO (UAX T4 ) 0.8957 msec/pass, best of ( 0.9226 0.8992 0.8957 ) ET : parse_stringIO (UAX T4 ) 5.6234 msec/pass, best of ( 5.6234 5.6872 5.6961 ) lxe: write_utf8_parse_stringIO (S-T T1 ) 189.2201 msec/pass, best of ( 199.9139 189.2201 190.3712 ) cET: write_utf8_parse_stringIO (S-T T1 ) 795.5032 msec/pass, best of ( 844.4007 824.9086 795.5032 ) ET : write_utf8_parse_stringIO (S-T T1 ) 1138.0186 msec/pass, best of ( 1140.2423 1141.4423 1138.0186 ) lxe: write_utf8_parse_stringIO (SAT T1 ) 190.7312 msec/pass, best of ( 192.9438 190.7312 193.4001 ) cET: write_utf8_parse_stringIO (SAT T1 ) 801.8634 msec/pass, best of ( 807.4269 803.6557 801.8634 ) ET : write_utf8_parse_stringIO (SAT T1 ) 1149.8636 msec/pass, best of ( 1149.8636 1150.1960 1161.8435 ) lxe: write_utf8_parse_stringIO (U-T T1 ) 187.6989 msec/pass, best of ( 187.6989 190.4670 190.4346 ) cET: write_utf8_parse_stringIO (U-T T1 ) 797.0220 msec/pass, best of ( 799.1436 797.0220 797.8761 ) ET : write_utf8_parse_stringIO (U-T T1 ) 1139.1940 msec/pass, best of ( 1139.1940 1143.0199 1144.4894 ) lxe: write_utf8_parse_stringIO (UAT T1 ) 192.8713 msec/pass, best of ( 192.8713 194.3054 193.6350 ) cET: write_utf8_parse_stringIO (UAT T1 ) 801.4468 msec/pass, best of ( 801.4468 801.8691 803.9093 ) ET : write_utf8_parse_stringIO (UAT T1 ) 1149.7449 msec/pass, best of ( 1152.1680 1208.7331 1149.7449 ) lxe: write_utf8_parse_stringIO (S-T T2 ) 197.3249 msec/pass, best of ( 198.7984 197.3249 199.2573 ) cET: write_utf8_parse_stringIO (S-T T2 ) 836.6382 msec/pass, best of ( 836.6382 839.7354 838.3641 ) ET : write_utf8_parse_stringIO (S-T T2 ) 1198.1185 msec/pass, best of ( 1201.7853 1200.2708 1198.1185 ) lxe: write_utf8_parse_stringIO (SAT T2 ) 220.1455 msec/pass, best of ( 220.1455 221.5693 221.5681 ) cET: write_utf8_parse_stringIO (SAT T2 ) 933.0841 msec/pass, best of ( 933.7380 937.9234 933.0841 ) ET : write_utf8_parse_stringIO (SAT T2 ) 1311.6351 msec/pass, best of ( 1311.6351 1314.4752 1314.5881 ) lxe: write_utf8_parse_stringIO (U-T T2 ) 200.4080 msec/pass, best of ( 200.4080 203.1036 200.5778 ) cET: write_utf8_parse_stringIO (U-T T2 ) 836.8698 msec/pass, best of ( 836.8698 838.9036 840.1444 ) ET : write_utf8_parse_stringIO (U-T T2 ) 1198.3584 msec/pass, best of ( 1198.3584 1200.3080 1206.1083 ) lxe: write_utf8_parse_stringIO (UAT T2 ) 218.4633 msec/pass, best of ( 222.4844 218.4633 275.0107 ) cET: write_utf8_parse_stringIO (UAT T2 ) 926.8864 msec/pass, best of ( 934.6416 926.8864 930.0010 ) ET : write_utf8_parse_stringIO (UAT T2 ) 1310.0202 msec/pass, best of ( 1312.2715 1317.1640 1310.0202 ) lxe: write_utf8_parse_stringIO (S-T T3 ) 12.0866 msec/pass, best of ( 12.1740 12.0866 12.2349 ) cET: write_utf8_parse_stringIO (S-T T3 ) 109.3471 msec/pass, best of ( 109.3471 109.3881 109.5528 ) ET : write_utf8_parse_stringIO (S-T T3 ) 226.3420 msec/pass, best of ( 226.3420 226.8248 228.9372 ) lxe: write_utf8_parse_stringIO (SAT T3 ) 61.4568 msec/pass, best of ( 61.7457 61.9032 61.4568 ) cET: write_utf8_parse_stringIO (SAT T3 ) 608.1295 msec/pass, best of ( 608.6636 608.1295 613.7108 ) ET : write_utf8_parse_stringIO (SAT T3 ) 825.5513 msec/pass, best of ( 825.8673 827.0674 825.5513 ) lxe: write_utf8_parse_stringIO (U-T T3 ) 12.0974 msec/pass, best of ( 12.1823 12.0974 12.1191 ) cET: write_utf8_parse_stringIO (U-T T3 ) 109.5899 msec/pass, best of ( 109.6426 109.7568 109.5899 ) ET : write_utf8_parse_stringIO (U-T T3 ) 226.3300 msec/pass, best of ( 226.4436 227.5431 226.3300 ) lxe: write_utf8_parse_stringIO (UAT T3 ) 61.9726 msec/pass, best of ( 64.3755 61.9726 62.0165 ) cET: write_utf8_parse_stringIO (UAT T3 ) 609.6428 msec/pass, best of ( 609.6428 609.8895 615.0596 ) ET : write_utf8_parse_stringIO (UAT T3 ) 824.3621 msec/pass, best of ( 824.5392 826.6240 824.3621 ) lxe: write_utf8_parse_stringIO (S-T T4 ) 0.4812 msec/pass, best of ( 0.4814 0.4812 0.4846 ) cET: write_utf8_parse_stringIO (S-T T4 ) 5.3454 msec/pass, best of ( 5.4478 5.3454 5.3874 ) ET : write_utf8_parse_stringIO (S-T T4 ) 7.9776 msec/pass, best of ( 8.0112 7.9776 8.0064 ) lxe: write_utf8_parse_stringIO (SAT T4 ) 1.7338 msec/pass, best of ( 1.7576 1.7409 1.7338 ) cET: write_utf8_parse_stringIO (SAT T4 ) 17.3748 msec/pass, best of ( 17.3826 17.3748 17.3764 ) ET : write_utf8_parse_stringIO (SAT T4 ) 22.7056 msec/pass, best of ( 22.7056 22.7506 22.7812 ) lxe: write_utf8_parse_stringIO (U-T T4 ) 0.4791 msec/pass, best of ( 0.4839 0.4873 0.4791 ) cET: write_utf8_parse_stringIO (U-T T4 ) 5.3264 msec/pass, best of ( 5.3264 5.3404 5.3775 ) ET : write_utf8_parse_stringIO (U-T T4 ) 8.0147 msec/pass, best of ( 8.0221 8.0147 8.0596 ) lxe: write_utf8_parse_stringIO (UAT T4 ) 1.7334 msec/pass, best of ( 1.7661 1.7767 1.7334 ) cET: write_utf8_parse_stringIO (UAT T4 ) 17.3602 msec/pass, best of ( 17.3602 17.3674 17.3672 ) ET : write_utf8_parse_stringIO (UAT T4 ) 22.6152 msec/pass, best of ( 22.6621 22.6913 22.6152 )

3 17

[lxml-dev] An intriguing behaviour of xpath in lxml
by Agustín Villena 01 Aug '06

01 Aug '06

Hi! Just a question. Assume the next code from lxml import etree from StringIO import StringIO xmlText = "<test>This is a test</test>" doc = etree.parse(StringIO(xmlText)) root = doc.xpath("/") The last line throws the next exception Not yet implemented result node type: 9 Traceback (most recent call last): File "C:\Archivos de programa\ActiveState Komodo 3.5\lib\support\dbgp\pythonlib\dbgp\client.py", line 1843, in runMain self.dbg.runfile(debug_args[0], debug_args) File "C:\Archivos de programa\ActiveState Komodo 3.5\lib\support\dbgp\pythonlib\dbgp\client.py", line 1538, in runfile h_execfile(file, args, module=main, tracer=self) File "C:\Archivos de programa\ActiveState Komodo 3.5\lib\support\dbgp\pythonlib\dbgp\client.py", line 596, in __init__ execfile(file, globals, locals) File "C:\dev\projects\python\python-xpath-example.py", line 7, in __main__ root = doc.xpath("/") File "c:\python24\lib\site-packages\lxml\etree.pyx", line 485, in etree._ElementTree.xpath File "c:\python24\lib\site-packages\lxml\xpath.pxi", line 75, in etree._XPathEvaluatorBase.evaluate File "c:\python24\lib\site-packages\lxml\xpath.pxi", line 212, in etree.XPathDocumentEvaluator.__call__ File "c:\python24\lib\site-packages\lxml\xpath.pxi", line 108, in etree._XPathEvaluatorBase._handle_result File "c:\python24\lib\site-packages\lxml\extensions.pxi", line 269, in etree._unwrapXPathObject File "c:\python24\lib\site-packages\lxml\extensions.pxi", line 317, in etree._createNodeSetResult NotImplementedError My question is: which is the reason behind this behaviour (if is there one)? (I already know that xpath(".") in the document node works, but is beyond my understanding why xpath("/") is not implemented. Cheers Agustin

3 3

Re: [lxml-dev] lxml - exslt - regexp:match()
by Stefan Behnel 01 Aug '06

01 Aug '06

Michael Zeidler wrote: > regexp:match('123abc567','([0-9]+)([a-z]+)([0-9]+)') gibt kein Arry mit den gematchten > Gruppen zurück: > Wenn ich also mit > <xsl:variable name="test" select="regexp:match('123abc567','([0-9]+)([a-z]+)([0-9]+)')"/> > die variable $test setzte, müsste ich mit $test[0], $test[1], usw. auf die gematchten gruppen > zugreifen können. Siehe http://www.exslt.org/regexp/functions/match/index.html > > [translation]: > > regexp:match('123abc567','([0-9]+)([a-z]+)([0-9]+)') > > does not return an array containing the matched groups. Something like this > <xsl:variable name="test" select="regexp:match('123abc567','([0-9]+)([a-z]+)([0-9]+)')"/> > should allow me to ask for "$test[0]" etc. > > See http://www.exslt.org/regexp/functions/match/index.html Hmm, interesting. The page doesn't actually say that this is supposed to work. All they provide is an example with a /single/ group. The result of your test case is not defined. For comparison, I now implemented the examples from the page as unit tests, which sadly showed that Python's regexps are incompatible with what EXSLT requires. The Python RE "([a-z])+ " does not match "test " as in EXSLT, only the last "t" is returned for the group by re.findall(). So we can't claim compatibility with EXSLT at this point. -- Note, though, that I never really said it was compatible, it just builds on Python's re module. I still think that's enough for a Python XML library. That said, I fixed your use case in the current trunk, as I think it makes sense to expect the result above from such a call. Note, however, that EXSLT dictates that the first element in a non-global RE result (without 'g' flag) must be the entire string that matched, which even fits the semantics of the group() method in Python's MatchObjects. So your $test[0] will contain "123abc567", $test[1] is "123" etc. Stefan

2 2

[lxml-dev] lxml eggs and unicode strings
by Martijn Faassen 31 Jul '06

31 Jul '06

Hi there, I just found out that there is a hidden incompatibility in the compiled versions of lxml eggs we provide, at least in linux. Our provided versions are compiled with a Python that has 4 bytes unicode support (probably the default on ubuntu on which I built the 2.4 extension). If you try to install such an egg on a machine where unicode support is compiled with 2 bytes only, it'll fail with errors such as: ImportError: /usr/local/lib/python2.4/site-packages/lxml-1.0.2-py2.4-linux-i686.egg/lxml/etree.so: undefined symbol: PyUnicodeUCS4_FromEncodedObject I wonder whether there's anything within the egg distribution mechanism that lets us distinguish between such platforms. If not, I wonder what to do instead -- the simplest would be to add a FAQ entry and tell people to recompile from the sources. By the way, does Pyrex generate different C code depending on whether 4 or 2 byte unicode is used? If so, then that would mean an installation of pyrex as well for these people... Regards, Martijn

4 9

Re: [lxml-dev] Compiling lxml with OpenOffice embeded python 2.3.4 runtime
by Olivier Collioud 28 Jul '06

28 Jul '06

Stefan, Thanks a lot for your help. Maybe I will try later to compile lxml for OO1.0.3/Py2.3.5, but I suspect that OO need to be compiled as well withe the same compiler. I would then prefer to make the effort to compile OO1.0.3 with Py2.4.3 (and then I would prefer by far someone to do it for me with a recent MS compiler ;-p). Now it has been decided to port my app to Java because all of our business apps run on this platform. Anyway, they have been impressed by the result, the performance and how fast I wrote this app which will be a key component of our business sw env. I did not succeed in convincing my collegues to use Python but we aggreed on a compromise by using Jython and Dom4j. It has been easy to switch so far because Lxml and Dom4j are quite similar API. Anyway, I hope I will have other opportunities to build some app based on Python/lxml which is my favourite XML dev toolkit (using also EclipseWTP and PyDev). And I would like to congratulate and thank you for the work done so far and your help. Kind regards, Olivier. >>> Stefan Behnel <behnel_ml(a)gkec.informatik.tu-darmstadt.de> 27/07/06 9:41 AM >>> Olivier Collioud wrote: > following these instructions: > http://codespeak.net/lxml/build.html#static-linking-on-windows > > Running these commands: [...] > C:\Download\lxml-source\lxml-1.0.2>python setup.py bdist_wininst --static > Building lxml version 1.0.2 [...] > File "C:\Program Files\OpenOffice.org > 2.0\program\python-core-2.3.4\lib\distutils\msvccompiler.py", line 118, > in set_macro > self.macros["$(%s)" % macro] = d[key] > KeyError: 'sdkinstallrootv1.1' > > My guess is that it is related to my MS-VS installation. It's the OOo SDK. You might have to install it: http://www.openoffice.org/dev_docs/source/sdk/ Stefan _______________________________________________ lxml-dev mailing list lxml-dev(a)codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev ------ World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.

2 1

[lxml-dev] Compiling lxml with OpenOffice embeded python 2.3.4 runtime
by Olivier Collioud 27 Jul '06

27 Jul '06

Hello, following these instructions: http://codespeak.net/lxml/build.html#static-linking-on-windows Running these commands: C:\Download\lxml-source\lxml-1.0.2>set PATH="C:\Program Files\OpenOffice.org 2.0\program";"C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\bin";"C:\Program Files\Microsoft Visual Studio\VC98\Bin" C:\Download\lxml-source\lxml-1.0.2>set PYTHONPATH="C:\Program Files\OpenOffice.org 2.0\program";"C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib" C:\Download\lxml-source\lxml-1.0.2>python setup.py bdist_wininst --static Building lxml version 1.0.2 *NOTE*: Trying to build without Pyrex, needs pre-generated 'src/lxml/etree.c' ! running bdist_wininst running build running build_py running build_ext Traceback (most recent call last): File "setup.py", line 170, in ? ext_modules = ext_modules, File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\core.py", line 149, in setup dist.run_commands() File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\dist.py", line 907, in run_commands self.run_command(cmd) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\dist.py", line 927, in run_command cmd_obj.run() File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\command\bdist_wininst.py", line 101, in run self.run_command('build') File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\cmd.py", line 333, in run_command self.distribution.run_command(command) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\dist.py", line 927, in run_command cmd_obj.run() File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\command\build.py", line 107, in run self.run_command(cmd_name) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\cmd.py", line 333, in run_command self.distribution.run_command(command) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\dist.py", line 927, in run_command cmd_obj.run() File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\command\build_ext.py", line 243, in run force=self.force) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\ccompiler.py", line 1173, in new_compiler return klass (None, dry_run, force) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\msvccompiler.py", line 206, in __init__ self.__macros = MacroExpander(self.__version) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\msvccompiler.py", line 112, in __init__ self.load_macros(version) File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\msvccompiler.py", line 128, in load_macros self.set_macro("FrameworkSDKDir", net, "sdkinstallrootv1.1") File "C:\Program Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib\distutils\msvccompiler.py", line 118, in set_macro self.macros["$(%s)" % macro] = d[key] KeyError: 'sdkinstallrootv1.1' My guess is that it is related to my MS-VS installation. I have no experience with MS compilation. (I don't even know why it is installed on my PC :-). I would be grateful if anybody can help me to build this or tell me where I can download an lxml 1.0.2 or more recent (or not too old) build for win32 and Python 2.3.4. Olivier. ------ World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.

2 2

Re: [lxml-dev] Compiling lxml with OpenOffice embeded python 2.3.4 runtime
by Olivier Collioud 27 Jul '06

27 Jul '06

Voici le résultat de la compilation après installation de python 2.3.5 C:\Download\lxml-source\lxml-1.0.2>python setup.py bdist_wininst --static Building lxml version 1.0.2 *NOTE*: Trying to build without Pyrex, needs pre-generated 'src/lxml/etree.c' ! running bdist_wininst running build running build_py running build_ext building 'lxml.etree' extension C:\Program Files\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Ox /MD /W3 /GX /DNDEBUG -IC:\soft\python23\include -IC:\soft\python23\PC /Tcsrc/l xml/etree.c /Fobuild\temp.win32-2.3\Release\src/lxml/etree.obj -w -I..\libxml2-2.6.26.win32\include -I..\libxslt-1.1.17.win32\include -I..\zlib-1.2.3. win32\include -I..\iconv-1.9.2.win32\include Command line warning D4025 : overriding '/W3' with '/w' etree.c C:\Program Files\Microsoft Visual Studio\VC98\BIN\link.exe /DLL /nologo /INCREMENTAL:NO /LIBPATH:C:\soft\python23\libs /LIBPATH:C:\soft\python23\PCBui ld /EXPORT:initetree build\temp.win32-2.3\Release\src/lxml/etree.obj /OUT:build\lib.win32-2.3\lxml\etree.pyd /IMPLIB:build\temp.win32-2.3\Release\src/ lxml\etree.lib ..\libxml2-2.6.26.win32\lib\libxml2_a.lib ..\libxslt-1.1.17.win32\lib\libxslt_a.lib ..\libxslt-1.1.17.win32\lib\libexslt_a.lib ..\zlib- 1.2.3.win32\lib\zlib.lib ..\iconv-1.9.2.win32\lib\iconv_a.lib Creating library build\temp.win32-2.3\Release\src/lxml\etree.lib and object build\temp.win32-2.3\Release\src/lxml\etree.exp LINK : warning LNK4049: locally defined symbol "_xmlFree" imported LINK : warning LNK4049: locally defined symbol "_xsltDocDefaultLoader" imported LINK : warning LNK4049: locally defined symbol "_xsltLibxsltVersion" imported libxslt_a.lib(numbers.obj) : error LNK2001: unresolved external symbol __ftol2 libexslt_a.lib(date.obj) : error LNK2001: unresolved external symbol __ftol2 libexslt_a.lib(strings.obj) : error LNK2001: unresolved external symbol __ftol2 libexslt_a.lib(math.obj) : error LNK2001: unresolved external symbol __ftol2 libxml2_a.lib(xpath.obj) : error LNK2001: unresolved external symbol __ftol2 libxml2_a.lib(xpointer.obj) : error LNK2001: unresolved external symbol __ftol2 libxml2_a.lib(xmlschemastypes.obj) : error LNK2001: unresolved external symbol __ftol2 libxslt_a.lib(xsltutils.obj) : error LNK2001: unresolved external symbol __ftol2 build\lib.win32-2.3\lxml\etree.pyd : fatal error LNK1120: 1 unresolved externals error: command '"C:\Program Files\Microsoft Visual Studio\VC98\BIN\link.exe"' failed with exit status 1120 >>> Stefan Behnel <behnel_ml(a)gkec.informatik.tu-darmstadt.de> 26/07/06 9:02 AM >>> Hi Olivier, Olivier Collioud wrote: > I have no experience with Python C extension compilation too. > > Do you mean that I do not need any C compiler to build this kind of > beast. No, en fait, je pensais plutôt que ça vaut le coup d'essayer avec un 'vrais' Python. Si le mystérieux "sdkinstallrootv1.1" vient de OOo, ça se peut que tu arriveras à utiliser un lxml compilé pour un python.org Python dans le OOo Python. Donc: Installer Python 2.3.4 'normal', compiler et installer lxml avec ça, et après copier le répertoire installé (site-packages/lxml) dans le Python de OOo. Stefan >>>> Stefan Behnel > Olivier Collioud wrote: >> following these instructions: >> http://codespeak.net/lxml/build.html#static-linking-on-windows >> >> Running these commands: >> >> C:\Download\lxml-source\lxml-1.0.2>set PATH="C:\Program >> Files\OpenOffice.org 2.0\program";"C:\Program Files\OpenOffice.org >> 2.0\program\python-core-2.3.4\bin";"C:\Program Files\Microsoft > Visual >> Studio\VC98\Bin" >> >> C:\Download\lxml-source\lxml-1.0.2>set PYTHONPATH="C:\Program >> Files\OpenOffice.org 2.0\program";"C:\Program Files\OpenOffice.org >> 2.0\program\python-core-2.3.4\lib" >> >> C:\Download\lxml-source\lxml-1.0.2>python setup.py bdist_wininst >> --static >> Building lxml version 1.0.2 > [...] >> File "C:\Program Files\OpenOffice.org >> 2.0\program\python-core-2.3.4\lib\distutils\msvccompiler.py", line > 118, >> in set_macro >> self.macros["$(%s)" % macro] = d[key] >> KeyError: 'sdkinstallrootv1.1' >> >> My guess is that it is related to my MS-VS installation. > > Looks like it. Though I'm not sure which 'sdk' is referred to here. > Might also > be the OOo SDK. > > >> I have no experience with MS compilation. (I don't even know why it > is >> installed on my PC :-). > > Guess you accidentally installed MS-Windows, that tends to install a > lot of > Microsoft stuff. ;) > > >> I would be grateful if anybody can help me to build this or tell me >> where I can download an lxml 1.0.2 or more recent (or not too old) > build >> for win32 and Python 2.3.4. > > We usually don't have Windows binaries for Python 2.3. Martijn keeps > building > Linux eggs for it, mainly to support Web-Servers, but most people are > on 2.4 > by now. > > What about installing a normal Python 2.3 (from python.org), build > lxml > against that and then just /install/ it to the OOo Python directory? > > Stefan > > _______________________________________________ > lxml-dev mailing list > lxml-dev(a)codespeak.net > http://codespeak.net/mailman/listinfo/lxml-dev > > > ------ > World Intellectual Property Organization Disclaimer: > > This electronic message may contain privileged, confidential and > copyright protected information. If you have received this e-mail > by mistake, please immediately notify the sender and delete this > e-mail and all its attachments. Please ensure all e-mail attachments > are scanned for viruses prior to opening or using. > > ------ World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.

2 2

[lxml-dev] Custom element class lookup mechanisms
by Stefan Behnel 27 Jul '06

27 Jul '06

Hi all, as I was working on the C-API anyway (capi branch), I decided to add a little external module with different ways of determining the Python element class for a libxml2 node. The "lxml.elements.classlookup" module currently implements three different ways of doing this: * ElementDefaultClassLookup always uses the default class * ElementNamespaceClassLookup is the default namespace lookup mechanism * AttributeBasedElementClassLookup determines the class by looking up the value of a specific attribute in a dict. It falls back to the default classes. Other ways are of cause possible, so if anyone has an idea what to add, I'm open for suggestions. An example usage is this: from lxml.elements import classlookup classlookup.setElementClassLookup( classlookup.ElementDefaultClassLookup()) It registers the mechanism that always uses the default class for elements, comments and PIs (yes, I implemented that, too). This disables the namespace class lookup and thus speeds up the plain element object creation by up to 10%. Example usage for attribute based lookup: mydict = {'int' : IntElement, 'str' : StrElement} classlookup.setElementClassLookup( classlookup.AttributeBasedElementClassLookup('pytype', mydict)) root = etree.XML('<x><a pytype="int">5</a><b pytype="str">test</b></x>') Internally, the lookup function is registered using the public C-API function "setElementClassLookupFunction()" and must be implemented in Pyrex (or C). It takes an object and the xmlNode* as arguments. The object can be used to keep some status, such as the attribute name and class dict in the AttributeBasedElementClassLookup case. It is registered together with the lookup function, passed as first argument on each call and otherwise ignored by lxml. The return value of the lookup function is a callable Python object (typically a subtype of _Element) that returns an element instance. The C API itself is briefly described here: http://codespeak.net/svn/lxml/branch/capi/doc/capi.txt Hope this is useful, Stefan

2 3

[lxml-dev] objectify feedback
by Martijn Faassen 26 Jul '06

26 Jul '06

Hi there, I just read through the objectify.txt documentation/doctest. Quite interesting and impressive stuff! One thing that worries me is that it does introduce quite a new API with different behavior than ElementTree in some fundamental ways. How close is the behavior of the new API to Amara? I'd be nice if we weren't inventing too much that's new here somehow.. Anyway, this is "are we inventing too many new wheels?" worry - one of the ideas of lxml is not to invent too many, though on the other hand we shouldn't stop people from building cool stuff on top of the core, which is what this is. The other thing that worries me from a more practical perspective is that this is, as far as I can see, controlled globally. The beginning of the document says "Don't mix!" and this sounds like sensible advice, but as far as I understand if you use objectify in your application you cannot use ElementTree anymore in the same application, unless you do a lot of registration and reset work. It'd be *very* nice if this were not so - create an objectified tree separately not affecting the way normal trees are created. This way, you could have one module of your application using objectify but another module still sticking to normal ElementTree. What to do when someone tries to mix bits of one tree with another? Perhaps there's an efficient way to compare baseclass between the two lxml objects that are combined, and bail out with some reasonably clear exception in case of illegal combinations. Regards, Martijn

2 2

Re: [lxml-dev] xml2 and xslt libraries
by Stefan Behnel 25 Jul '06

25 Jul '06

Hi Asif, Asif Iqbal wrote: > I could not compile . I attached the compile output called lxml.compile.out Hmm, ok, first things first: 3MB log files are not quite the thing you should send to a mailing list. That's something for a) private e-mail and b) compressors like bzip2, which, BTW, compresses it to some 100K. That said, here's the relevant portions: ------------------------------------- Building lxml version 1.0.2 running build_ext building 'lxml.etree' extension gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I/usr/local/include/python2.4 -c src/lxml/etree.c -o build/temp.solaris-2.10-i86pc-2.4/src/lxml/etree.o -w -I/usr/local/include/libxml2 -I/usr/local/include/libxslt -I/usr/loc al/include/libexslt -I/usr/local/include/python2.4 -I/usr/include gcc -shared build/temp.solaris-2.10-i86pc-2.4/src/lxml/etree.o -o build/lib.solaris-2.10-i86pc-2.4/lxml/etree.so -L/usr/local/lib/python2.4 /usr/local/lib/libexslt.a /usr/local/lib/libxslt.a /usr/local/lib/libxml2.a -lz -lpthread -lsocket -lnsl -lm Text relocation remains referenced against symbol offset in file <unknown> 0x17 /usr/local/lib/libexslt.a(common.o) <unknown> 0xb6 /usr/local/lib/libexslt.a(common.o) <unknown> 0xe3 /usr/local/lib/libexslt.a(common.o) <unknown> 0x11c /usr/local/lib/libexslt.a(common.o) [...] fmod 0x7f3b /usr/local/lib/libxml2.a(xpath.o) fmod 0x8023 /usr/local/lib/libxml2.a(xpath.o) fmod 0x8c6c /usr/local/lib/libxml2.a(xpath.o) ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 ------------------------------------- Hmmm, don't know where that comes from. I can see that you added quite a number of libraries and I don't think it's because there is one missing. Maybe someone else who has more experience with Solaris compilation than I do could help you here... > Looks like 1.0.2 needed a patch to > > --- setup.py.orig Tue Jul 25 08:03:15 2006 > +++ setup.py Tue Jul 25 08:03:29 2006 > @@ -18,7 +18,7 @@ > xslt_libs = [ > ] > result = (cflags, xslt_libs) > - # return result > + return result > raise NotImplementedError, \ > "Static build not configured, see doc/build.txt" No, why? There is no standard configuration for static compilation, so you get an exception when you pass "--static" until you managed to a) read the docs and b) changed the static setup function accordingly. Stefan

1 0