➜

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 vstinner
Recipients benjamin.peterson, brett.cannon, corona10, rhettinger, serhiy.storchaka, vstinner
Date 2019-12-06.17:43:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1575654226.05.0.233487616929.issue38916@roundup.psfhosted.org>
In-reply-to
Content 
> If it was documented as deprecated and raising a deprecation warning then 3.2 is definitely far enough back to warrant removing it.

Exactly. I'm in favor of removing fromstring() and tostring() methods right now, and update 3.7 and 3.8 documentation to mention that the methods are removed in Python 3.9, not Python 4.0.

Either do it right now, or wait the beginning of the next Python 3.x release cycle. I prefer to push some incompatible changes at the beginning of dev cycles, to get enough time to measure the feedback from users.

--

Brett opened a more generic discussion about the deprecation process, since PEP 602 has been accepted:
https://mail.python.org/archives/list/python-dev@python.org/thread/BRA7G4UIGGW2X7YY55KQZBOGJEYNUV6O/
History
Date User Action Args
2019-12-06 17:43:46vstinnersetrecipients: + vstinner, brett.cannon, rhettinger, benjamin.peterson, serhiy.storchaka, corona10
2019-12-06 17:43:46vstinnersetmessageid: <1575654226.05.0.233487616929.issue38916@roundup.psfhosted.org>
2019-12-06 17:43:46vstinnerlinkissue38916 messages
2019-12-06 17:43:45vstinnercreate