Anders Hovmöller <bo...@killingar.net> added the comment: We were also bitten by this. In fact we still run a compatibility shim in production where we log if the new and old behavior are different. We also didn't think this "bug fix" made sense or was treated with the appropriate gravity in the release notes.
I understand the logic in the bug tracker and they it matches other languages is good. But the bahvior also makes no sense for the .* case unfortunately. > On 21 Jan 2020, at 05:56, David Barnett <rep...@bugs.python.org> wrote: > > > David Barnett <davidbarne...@gmail.com> added the comment: > > We were also bitten by this behavior change in > https://github.com/google/vroom/issues/110. I'm kinda baffled by the new > behavior and assumed it had to be an accidental regression, but I guess not. > If you have any other context on the BDFL conversation and reasoning for > calling this behavior correct, I'd love to see additional info. > > ---------- > nosy: +mu_mind > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue32308> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32308> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
