Steve Dower <steve.do...@python.org> added the comment:
If we should put in the workaround for 3.8, how does that make it okay to remove in 3.9? It's been deprecated since 3.0 already, so if we can't remove it after eight releases, I don't see how it's consistent to remove it after a ninth. Once we put it back, it basically has to stay. The middle ground doesn't make sense. We should either replace it with the new field, or put the new field at the end and leave the deprecated one exactly as it was. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37250> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
