On Wed, Dec 24, 2008 at 4:43 AM, Edward Z. Yang <edwardzy...@thewritingpot.com> wrote: > > I went ahead and ran the test suite against the Python implementation to > see whether or not Python got 100% passes on test_tokenizer.py. It > didn't. In fact, it didn't even finish, because I got a fatal exception > "'ascii' codec can't encode characters in position 22-23: ordinal not in > range(128)". This seems pretty bad, and certainly not the "one test > failure" mentioned in 0.11 Known Issues. > > I'm running on Python 2.5.2, on Windows Vista courtesy of Cygwin. What's up?
Oops, I had added some test cases with non-ASCII characters in their
descriptions, which unittest.py doesn't like. Fixed that now.
I get 109 failures when running on Windows, seemingly caused by
Unicode issues, along the lines of:
Expected: [u'ParseError', [u'StartTag', u'a\U00100000', {}]]
Received: [u'ParseError', u'ParseError', u'ParseError',
[u'StartTag', u'a\U00100000', {}]]
but I don't really know what the problem is or how to fix it. (All the
tests pass correctly for me on Linux.)
--
Philip Taylor
exc...@gmail.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"html5lib-discuss" group.
To post to this group, send email to html5lib-discuss@googlegroups.com
To unsubscribe from this group, send email to
html5lib-discuss+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/html5lib-discuss?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4