© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
Ohad: yep, that seems potentially related to me. I saw the same behaviour (ASCII characters from the original input, separated by spaces, in the parsed text output) when using locally-compiled versions of lxml on OSX during investigation of the bug.