STINNER Victor <vstin...@python.org> added the comment:
> 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-...@python.org/thread/BRA7G4UIGGW2X7YY55KQZBOGJEYNUV6O/ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38916> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
