Message322593
Note: if you found a regexp like this _in_ the Python distribution, then a bug report would be appropriate. It's certainly possible to write regexps that can suffer catastrophic backtracking, and we've repaired a few of those, over the years, that shipped with Python.
But we can't stop you from writing such things yourself. If you post your regexp to, e.g., comp.lang.python or StackOverflow, I'm sure someone will show you how to rewrite it in a safe way. But be prepared to explain in English what you're trying to accomplish with it.
For example, while it appears you're trying to ensure there are at least 3 characters (of the right kind) between "|" separators, for some reason you made matching "|" optional. That leaves open an exponential number of ways to try to match long strings of non-"|" characters between "|" separators. |
|
Date |
User |
Action |
Args |
2018-07-28 22:25:48 | tim.peters | set | recipients:
+ tim.peters, taleinat, ezio.melotti, mrabarnett, serhiy.storchaka, ghi5107 |
2018-07-28 22:25:48 | tim.peters | set | messageid: <1532816748.06.0.56676864532.issue33113@psf.upfronthosting.co.za> |
2018-07-28 22:25:48 | tim.peters | link | issue33113 messages |
2018-07-28 22:25:47 | tim.peters | create | |
|