On Sun, Feb 24, 2019 at 10:04 PM Eric Snow wrote:
> I'll take a look tonight.
I made 2 successive runs of the script (on my laptop) for a commit
from early Saturday, and 2 runs from a commit this afternoon (close to
master). The output is below, with the earlier commit first. That
one is a litt
I'll take a look tonight.
-eric
On Sun, Feb 24, 2019, 21:54 Raymond Hettinger
wrote:
> I'll been running benchmarks that have been stable for a while. But
> between today and yesterday, there has been an almost across the board
> performance regression.
>
> It's possible that this is a measure
I'll been running benchmarks that have been stable for a while. But between
today and yesterday, there has been an almost across the board performance
regression.
It's possible that this is a measurement error or something unique to my system
(my Mac installed the 10.14.3 release today), so
On Sun, Feb 24, 2019 at 5:09 AM Davin Potts <
python+python_...@discontinuity.net> wrote:
> I have done what I was asked to do: I added tests and docs in a new
> PR (GH-11816) as of Feb 10.
>
> Since that time, the API has matured thanks to thoughtful feedback
> from a number of active reviewers.
On Sun, Feb 24, 2019 at 1:07 PM Terry Reedy wrote:
> On 2/23/2019 2:50 PM, Cheryl Sabella wrote:
>
> AM Karthikeyan wrote:
> > I would also recommend waiting for a core dev or someone to provide
> > some feedback or confirmation on even an easy issue's fix since it's
> > easy to pr
