Message233434
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. |
|
Date |
User |
Action |
Args |
2015-01-04 22:51:36 | martin.panter | set | recipients:
+ 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:35 | martin.panter | set | messageid: <1420411895.86.0.378005372428.issue13248@psf.upfronthosting.co.za> |
2015-01-04 22:51:35 | martin.panter | link | issue13248 messages |
2015-01-04 22:51:35 | martin.panter | create | |
|