➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients Arfrever, BreamoreBoy, berker.peksag, eric.araujo, ezio.melotti, flox, giampaolo.rodola, larry, martin.panter, orsenthil, pitrou, python-dev, rhettinger, terry.reedy, tshepang, vstinner
Date 2015-01-04.22:51:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420411895.86.0.378005372428.issue13248@psf.upfronthosting.co.za>
In-reply-to
Content 
Another one to deal with one way or the other: html.parser.HTMLParser.unescape()

It is apparently due to be removed in 3.5. It was meant to be an undocumented internal function, and there is now an public alternative. However I would be inclined to leave it around a little longer, because it seems to have been widely recommended for decoding HTML entities in the past (e.g. <https://wiki.python.org/moin/EscapingHtml>), and keeping it would simplify maintaining Python 2 compatible code.
History
Date User Action Args
2015-01-04 22:51:36martin.pantersetrecipients: + martin.panter, rhettinger, terry.reedy, orsenthil, pitrou, vstinner, larry, giampaolo.rodola, ezio.melotti, eric.araujo, Arfrever, flox, BreamoreBoy, tshepang, python-dev, berker.peksag
2015-01-04 22:51:35martin.pantersetmessageid: <1420411895.86.0.378005372428.issue13248@psf.upfronthosting.co.za>
2015-01-04 22:51:35martin.panterlinkissue13248 messages
2015-01-04 22:51:35martin.pantercreate