Hi Łukasz, As we have to a decision here, my vote is to revert the patch in 3.8.2 and 3.7.7 I have gone back-and-forth with this thinking, and it seems revert might address some definite complaints we have got. The problem is contained to single version, and users can upgrade to the next one.
Thanks, Senthil On Fri, Feb 14, 2020 at 8:14 AM Łukasz Langa <luk...@langa.pl> wrote: > Ned, what are you doing with this for 3.7.7? Reverting? > > - Ł > > > > On 13 Feb 2020, at 22:18, Barry Warsaw <ba...@python.org> wrote: > > > > On Feb 11, 2020, at 05:26, Łukasz Langa <luk...@langa.pl> wrote: > >> > >> I'll let others voice their opinions but my intuition for 3.8.x is to > leave your patch be. True, it should not have been backported but it was, > and it was already released as part of 3.8.1 and now 3.8.2rc1. > > > > I don’t think you should worry about 3.8.2rc1. That’s not a release > version so shouldn’t impact the decision IMHO. > > > > Whether 3.8.1 is important enough not to revert this change is an RM > decision. > > > > -Barry > > > >
_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/VT3W2MZXZYNZD3L3MCUY2G2A2JGYT7JT/ Code of Conduct: https://www.python.org/psf/codeofconduct/
