The most important part of my previous comment, four years ago, that review was needed from Larry Hastings (or someone who understood the current code) ,was ignored. Until it is determined whether any change to the re is acceptable, it is useless to discuss the exact change. This PR seems premature. I think I should have suggested a core-workflow issue.

According to dates in author:larryhastings search query for commits and for issues, he fortunately seems to be relatively active, just dedicated exclusively to other projects.

@larryhastings Would you mind to review and possibly merge this PR or gh-291 alternative please? Both are one-liners.

@larryhastings ping?

FWIW, the tauthon repo hasn't seen any PR or commit activity in nearly 6 months, and only a handful of commits all by a single person in the past year+ since the final release of CPython 2.7, so it's unclear how useful this will be to them at this point. However, it could be useful for other forks that have names ending in thon (though many don't, e.g. Pyston, no-gil, etc.)

I've pinged @larryhastings through other channels, but I also want to mention @gpshead who previously reviewed and approved a previous fairly small PR similar to this one, given this is seemingly just a trivial regex.

@larryhastings ping?

ping