This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Anders.Hovmöller
Recipients Anders.Hovmöller, ezio.melotti, mrabarnett, mu_mind, serhiy.storchaka
Date 2020-01-21.06:07:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
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 <> wrote:
> David Barnett <> added the comment:
> We were also bitten by this behavior change in 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 <>
> <>
> _______________________________________
Date User Action Args
2020-01-21 06:07:35Anders.Hovmöllersetrecipients: + Anders.Hovmöller, ezio.melotti, mrabarnett, mu_mind, serhiy.storchaka
2020-01-21 06:07:35Anders.Hovmöllerlinkissue32308 messages
2020-01-21 06:07:35Anders.Hovmöllercreate