[lxml-dev] lxml 1.1 problems with python 2.3
Martijn Faassen
faassen at infrae.com
Thu Nov 30 18:09:03 CET 2006
Hey Stefan,
Stefan Behnel wrote:
> Martijn Faassen wrote:
>> Did you forget to check in local_doctest.py?
>
> No, it's right in src/, revision 35023. It's a copy of the one you put into
> revision 8449.
>
> Maybe it's just not found in the PYTHONPATH? (Well, test.py should do that for
> us, right?)
Stupid of me not to see it earlier, but that's because it's trying to
import from lxl.local_doctest and you added it as local_doctest. I fixed
the import not to import from the lxml namespace anymore and checked it
in. That still leaves the next error.
>> Things then fail with what looks like a new, unrelated issue:
>>
>> Traceback (most recent call last):
>> File "test.py", line 591, in ?
>> exitcode = main(sys.argv)
>> File "test.py", line 554, in main
>> test_cases = get_test_cases(test_files, cfg, tracer=tracer)
>> File "test.py", line 254, in get_test_cases
>> module = import_module(file, cfg, tracer=tracer)
>> File "test.py", line 197, in import_module
>> mod = __import__(modname)
>> File
>> "/home/faassen/working/lxml/lxml-trunk/src/lxml/tests/test_objectify.py",
>> line 16, in ?
>> from lxml import objectify
>> ImportError:
>> /home/faassen/working/lxml/lxml-trunk/src/lxml/objectify.so: undefined
>> symbol: previousElement
>
> That's rather bizarre, previousElement is definitely a public function (i.e.
> defined in etree.so). I have no idea how that could be missing.
It's consistently missing though in Python 2.3. Perhaps it accidentally
gets turned off together with thread support? I did try to test this
theory yesterday though on Python 2.4 by explicitly disabling tests, and
that didn't help.
Regards,
Martijn
More information about the lxml-dev
mailing list