-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="im"><br>
On 07/29/2011 07:22 AM, Joao S. O. Bueno wrote:<br>
<br>
> I disaagree. Having proper html parsing out of the box is part of<br>
> the "batteries included" thing. And it is not a matter of "having<br>
> html 5" - as stated on this thread, fixing it for html5 will fix it<br>
> for html that exists in the "real world".<br>
><br>
> Python _has_ to work with quick 30-50 lines scripts deliverable<br>
> everywhere, not just has proper 3rd party libraries that can work as<br>
> part of a huge project using buildout.<br>
<br>
</div>Assuming it were merged today, that parser would only be available on<br>
Python 3.3 and later: how is that "everywhere"?</blockquote><div><br>Well, "everywhere, eventually". This gets down to the usual philosophical debate of what should (not) be in the stdlib so that those who have strict third-party code get access to useful libraries while balancing the desire of those who want to keep the stdlib lean or prevent stagnating the API of a module.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Having scripts that<br>
work against html5lib (which *doesn't* need buildout to install, or even<br>
setuptools) makes them portable to any version of Python supported by<br>
the library (Python 2.3+, AFAICT).<br></blockquote><div><br>If the library was brought in they could probably continue to be portable with possibly just the addition of a try/finally on the import line.<br><br>-Brett<br>