Showing content from http://mail.python.org/pipermail/python-dev/attachments/20090302/a38b8adf/attachment.htm below:
<br><br><div class="gmail_quote">On Mon, Mar 2, 2009 at 04:23, Vaibhav Mallya <span dir="ltr"><<a href="mailto:vaibhavmallya@gmail.com">vaibhavmallya@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I haven't seen a lot of discussion on this - maybe I didn't search hard enough - but  what are people's thoughts on including BeautifulSoup in stdlib? It's small, fast, and pretty widely-liked by the people who know about it. Someone mentioned that web scraping needs are infrequent. My argument is that people ask questions about them less because they feel they can just reinvent the wheel really easily using urllib and regexes. It seems like this is similar to the CSV problem from a while back actually, with everyone implementing their own parsers.<br>
<br>
We do have HTMLParser, but that doesn't handle malformed pages well, and just isn't as nice as BeautifulSoup.<br>
<br>
In a not-entirely-unrelated vein, has there been any discussion on just throwing all of Mechanize into stdlib?</blockquote><div><br>Discussions of including modules in the standard library only occurs when the module creators step forward to offer to support the modules. To my knowledge neither the creators of BeautifulSoup or Mechanize have come forward to offer to manage the code in Python's standard library.<br>
<br>-Brett <br></div></div><br>
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