FWIW, I agree with Senthil here. A slight behaviour change in 3.9 is fine, especially in an area where the "right" semantics are not immediately obvious. What we want to avoid is breaking behaviour changes in bugfix releases.
Regards Antoine. Le 16/02/2020 à 13:13, Senthil Kumaran a écrit : > > On Sun, Feb 16, 2020 at 2:20 AM Ned Deily <n...@python.org > <mailto:n...@python.org>> wrote: > > > > For 3.9.0, I recommend we reconsider this change (temporarily > reverting it) and consider whether an API change to accommodate the > various use cases would be better > > > For 3.9. - I am ready to defend the patch even at the cost of the > breaking of the parsing of undefined behavior. We should keep it. The > patch simplifies a lot of corner cases and fixes the reported bugs. We > don't guarantee backward compatibility between major versions, so I > assume users will be careful when relying upon this undefined behavior > and will take corrective action on their side before upgrading to 3.9. > > We want patch releases to be backward compatible. That was the > user-complaint. > > Thanks, > Senthil > > > > _______________________________________________ > 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/SQE6TKOYZKEFGWMUHU5RCHRVWJ27TIQV/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > _______________________________________________ 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/P6N7GWW5RQ66467NXYJPHV6JKBY4QM27/ Code of Conduct: https://www.python.org/psf/codeofconduct/
