On Wed, 7 Aug 2019 at 10:32, Steven D'Aprano <st...@pearwood.info> wrote:
> No, I'm saying we don't have to rush this into 3.8. Let's keep the > warning silent and push everything back a release. > > Now is better than never. > Although never is often better than *right* now. > > Right now, we're looking at a seriously compromised user-experience for > 3.8. People are going to hate these warnings, many of them won't know > what to do with them and will be sure that Python is buggy, and for very > little benefit. > > Let's slow down and put it off for another release, giving us time to > solve the warnings problem, and library authors the deprecation period > promised. +1 from me. The arguments made here are pretty compelling to me, and I agree that we should take a breath and not rush this warning into 3.8, given what we now know. Paul _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/OXGY2MPRTK3BJAXCRVLFKKKQNREKO7O4/
