Nick Coghlan added the comment:
George's initial patch that naively checks for signals on every iteration could
be used to get an upper bound on the likely benchmark impact.
I do think this is a case where we'll want a dedicated microbenchmark to
complement the macrobenchmark suite, though - Raymond's right that these
functions are frequently used to optimise sections of code that have already
been identified as performance bottlenecks in a particular application, so we
need to be really careful with changes that might make them slower (even if the
current macrobenchmarks say things are still broadly OK).
Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list