On 17 Nov 2015, at 21:22, Stewart, David C <david.c.stewart at intel.com> wrote: > On 11/17/15, 10:40 AM, "Python-Dev on behalf of R. David Murray" <python-dev-bounces+david.c.stewart=intel.com at python.org on behalf of rdmurray at bitdance.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. --David
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