<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 10, 2011, at 6:30 PM, Terry Reedy wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">A little data: the HTML5lib project lives at<br><a href="https://code.google.com/p/html5lib/">https://code.google.com/p/html5lib/</a><br>It has 4 owners and 22 other committers.<br><br>The most recent release, html5lib 0.90 for Python, is nearly 2 years old. Since there is a separate Python3 repository, and there is no mention on Python3 compatibility elsewhere that I saw, including the pypi listing, I assume that is for Python2 only.<br></span></span></blockquote><div><br></div><div>I believe that you are correct.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">A comment on a recent (July 11) Python3 issue<br><a href="https://code.google.com/p/html5lib/issues/detail?id=187&colspec=ID Type Status Priority Milestone Owner Summary Port">https://code.google.com/p/html5lib/issues/detail?id=187&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Port</a><br>suggest that the Python3 version still has problems. "Merged in now, though still lots of errors and failures in the testsuite."<br></span></span></blockquote></div><div><br></div><div>I don't see what bearing this has on the discussion. There are three possible ways I can imagine to interpret this information.</div><div><br></div><div>First, you could believe that porting a codebase from Python 2 to Python 3 is much easier than solving a difficult domain-specific problem. In that case, html5lib has done the hard part and someone interested in html-in-the-stdlib should do the rest.</div><div><br></div><div>Second, you could believe that porting a codebase from Python 2 to Python 3 is <i>harder</i> than solving a difficult domain-specific problem, in which case something is seriously wrong with Python 3 or its attendant migration tools and <i>that</i> needs to be fixed, so someone should fix that rather than worrying about parsing HTML right now. (I doubt that many subscribers to this list would share this opinion, though.)</div><div><br></div><div>Third, you could believe that parsing HTML is not a difficult domain-specific problem. But only a crazy person would believe that, so you're left with one of the previous options :).</div><div><br></div><div>-glyph</div><div><br></div></body></html>