I wonder if removing HTMLParser().unescape() would hurt Python 2 → 3 compatibility. This was mentioned in Ezio’s draft deprecation policy PEP <https://mail.python.org/pipermail/python-committers/2016-January/003706.html\>: “nothing that is available and not deprecated in 2.7 should be removed from Python 3 as long as 2.7 is officially supported”.
Is there any pressing need to get rid of the method? Maybe just fix the reference to Python 3.5 for the time being.
The backport to 3.9 is still pending. The bot claims that there is a merge conflict. This should not happen because What's New in 3.9 should be identical in master and 3.9. My guess is that someone only changed it in 3.9, though another change in master might not have been backported. I will try to determine the problem.
Activity
serhiy-storchaka commented on May 15, 2016
Proposed patch removes the unescape() method in the html.parser.HTMLParser class. This was deprecated since Python 3.4 (bpo-19688).
jimjjewett commented on May 23, 2016
Looks Good To Me
vadmium commented on May 25, 2016
I wonder if removing HTMLParser().unescape() would hurt Python 2 → 3 compatibility. This was mentioned in Ezio’s draft deprecation policy PEP <https://mail.python.org/pipermail/python-committers/2016-January/003706.html\>: “nothing that is available and not deprecated in 2.7 should be removed from Python 3 as long as 2.7 is officially supported”.
Is there any pressing need to get rid of the method? Maybe just fix the reference to Python 3.5 for the time being.
serhiy-storchaka commented on May 25, 2016
Good point. Maybe the deprecation period of HTMLParser.unescape() should be prolonged.
On other side, this method is not documented, nor in 2.7, nor in 3.x. It is not a part of official API.
bitdancer commented on May 25, 2016
Nevertheless, our current standing policy is to not remove anything until after 2.7 goes out of maintenance entirely.
berkerpeksag commented on May 25, 2016
It was removed before and added back with a deprecation warning (because someone was using it).
A little bit off-topic, but it would be great to have a "deprecated APIs in Python 3" list somewhere in the Python documentation (see https://docs.djangoproject.com/en/dev/internals/deprecation/ for an example).
iritkatriel commented on Sep 16, 2020
This was pending Python 2 EOL, so should be ok to do now, right?
orsenthil commented on Sep 16, 2020
Irit, yes. Serhiy's patch could be converted to a GitHub PR and it can be merged.
serhiy-storchaka commented on Sep 17, 2020
It was already removed in bpo-37328. The only not applied part of the patch is adding a What's New entry.
serhiy-storchaka commented on Sep 17, 2020
New changeset a33f2c2 by Serhiy Storchaka in branch 'master':
bpo-27032, bpo-37328: Document removing HTMLParser.unescape(). (GH-22288)
a33f2c2
iritkatriel commented on Sep 17, 2020
This issue can be closed now.
terryjreedy commented on Sep 17, 2020
The backport to 3.9 is still pending. The bot claims that there is a merge conflict. This should not happen because What's New in 3.9 should be identical in master and 3.9. My guess is that someone only changed it in 3.9, though another change in master might not have been backported. I will try to determine the problem.
terryjreedy commented on Sep 18, 2020
New changeset 4daeb9e by Terry Jan Reedy in branch '3.9':
[3.9] bpo-27032, bpo-37328: Document removing HTMLParser.unescape() (GH-22288)
4daeb9e
ambv commented on Oct 5, 2020
New changeset 8dd4302 by Łukasz Langa (Terry Jan Reedy) in branch '3.9':
[3.9] bpo-27032, bpo-37328: Document removing HTMLParser.unescape() (GH-22288)
8dd4302