On Mon, Feb 25, 2019 at 10:42 AM Eric Snow wrote:
> I'll look into it around then too. See https://bugs.python.org/issue33608.
I ran the "performance" suite (https://github.com/python/performance),
which has 57 different benchmarks. In the results, 9 were marked as
"significantly" different bet
On 2/21/19 2:26 AM, Michael wrote:
Will this continue to be enough space - i.e., is the Dev size going to
be enough?
+2042 #ifdef MS_WINDOWS
+2043 PyStructSequence_SET_ITEM(v, 2,
PyLong_FromUnsignedLong(st->st_dev));
+2044 #else
+2045 PyStructSequence_SET_ITEM(v, 2, _PyLong_
I packaged another release. Go get it here:
https://www.python.org/downloads/release/python-380a2/
Python 3.8.0a2 is the second of four planned alpha releases of Python 3.8,
the next feature release of Python. During the alpha phase, Python 3.8
remains under heavy development: additional features
Hi,
just curious on this,
On 2/25/19 5:54 AM, 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 measurement error or s
On Mon, Feb 25, 2019 at 10:32 AM Raymond Hettinger
wrote:
> I got it down to two checkins before running out of time:
>
> Between
> git checkout 463572c8beb59fd9d6850440af48a5c5f4c0c0c9
>
> And:
> git checkout 3b0abb019662e42070f1d6f7e74440afb1808f03
>
> So the subinterpreter patch was lik
> On Feb 25, 2019, at 2:54 AM, Antoine Pitrou wrote:
>
> Have you tried bisecting to find out the offending changeset, if there
> any?
I got it down to two checkins before running out of time:
Between
git checkout 463572c8beb59fd9d6850440af48a5c5f4c0c0c9
And:
git checkout 3b0abb019
On Sun, 24 Feb 2019 20:54:02 -0800
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.
Have you tried bisecting to find out the offending changeset, i
On Sat, 23 Feb 2019 22:09:03 -0600
Davin Potts 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. At present, we appear to have
> s
Hi,
Le lun. 25 févr. 2019 à 05:57, Raymond Hettinger
a écrit :
> 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.
How do you run your benchmarks? If you use Linux, are you usi
> On Feb 24, 2019, at 10:06 PM, Eric Snow wrote:
>
> I'll look into it in more depth tomorrow. FWIW, I have a few commits
> in the range you described, so I want to make sure I didn't slow
> things down for us. :)
Thanks for looking into it.
FWIW, I can consistently reproduce the results sev
Karthikeyan writes:
> I would also recommend waiting for a core dev or someone to provide some
> feedback or confirmation on even an easy issue's fix
FWIW, I don't think waiting on core devs is a very good idea, because
we just don't have enough free core dev time, and I don't think we (or
any
11 matches
Mail list logo
