Agreed with @p-ganssle . Similar issue33152 in the past for the refactoring in timeit module to use list comprehension. Large refactorings like this could also make git blame little more difficult in places where this has less benefit like smaller lists for common cases. I think it's much better to identify hot code paths with potentially large lists that could benefit from this along with a benchmark that could be accepted by the core dev/maintainer of the module.