On 17 Nov 2015, at 21:22, Stewart, David C email@example.com wrote:
On 11/17/15, 10:40 AM, "Python-Dev on behalf of R. David Murray" <firstname.lastname@example.org on behalf of email@example.com> wrote:
I suppose that for this to have maximum effect someone would have to specifically be paying attention to performance and figuring out why every (real) regression happened. I don't suppose we have anyone in the community currently who is taking on that role, though we certainly do have people who are *interested* in Python performance :)
We're trying to fill that role as much as we can. When there is a significant (and unexplained) regression that we see, I usually ask our engineers to bisect it to identify the offending patch and root-cause it.
That's great news.