Public bug reported:
As documented on
http://www.crummy.com/software/BeautifulSoup/3.1-problems.html the 3.1
BeautifulSoup branch uses a different parser to be compatible with
Python 3. Unfortunately this parser does much worse on invalid html than
the old one did, and a very common reason to use BeautifulSoup at all is
to parse invalid html. Upstream recommends either using the latest 3.0.x
BeautifulSoup (3.0.7a at time of writing) or some other library. I think
providing BeautifulSoup 3.0.x by default (providing BeautifulSoup under
a different name) would make sense, given the number of people on
freenode's #python I've had to link to
http://www.crummy.com/software/BeautifulSoup/3.1-problems.html already.
** Affects: beautifulsoup (Ubuntu)
Importance: Undecided
Status: New
--
beautifulsoup 3.1 is buggy, provide 3.0 by default
https://bugs.launchpad.net/bugs/392968
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
