Jeremy> The two default filters use the regular expression "". So we're
Jeremy> getting absolutely no benefit from those regular expressions. I
Jeremy> propose to modify the two regex slots in the filter tuple to
Jeremy> also store None, where None means matching anything.
Why bother compiling the regular expressions ahead of time? Just store
strings and use re.match(...) instead of pat.match(...). When you encounter
a potential warning you want to suppress, I suspect it's not generally going
to be in a speed critical part of the system. If it is a potential
performance issue, the re module will have the compiled regular expression
in its cache.
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4