➜

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 Jim.Jewett, ezio.melotti, martin.panter, serhiy.storchaka
Date 2016-05-25.09:40:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464169254.14.0.144911400798.issue27032@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2016-05-25 09:40:54martin.pantersetrecipients: + martin.panter, ezio.melotti, Jim.Jewett, serhiy.storchaka
2016-05-25 09:40:54martin.pantersetmessageid: <1464169254.14.0.144911400798.issue27032@psf.upfronthosting.co.za>
2016-05-25 09:40:54martin.panterlinkissue27032 messages
2016-05-25 09:40:54martin.pantercreate