On Thu, Sep 20, 2018 at 2:10 PM Wes Turner wrote:
>
> On Thursday, September 20, 2018, Stefan Ring wrote:
>>
>> On Tue, Sep 18, 2018 at 8:38 AM INADA Naoki wrote:
>>
>> > I think this topic should split to two topics: (1) Guard Python
>> > process from Spectre/Meltdown
>> > attack from other pro
Larry Hastings schrieb am 14.09.2018 um 23:27:
> What the patch does: it takes all the Python modules that are loaded as
> part of interpreter startup and deserializes the marshalled .pyc file into
> precreated objects stored as static C data.
What about the small integers cache? The C serialisati
Carl Shapiro schrieb am 20.09.2018 um 20:21:
> On Wed, Sep 19, 2018 at 12:32 AM, Stefan Behnel wrote:
>
>> Also, one thing that would be interesting to find out is whether constant
>> Python data structures can actually be pre-allocated in the data segment
>> (and I mean their object structs) . Th
On Wed, Sep 19, 2018 at 12:32 AM, Stefan Behnel wrote:
> Also, one thing that would be interesting to find out is whether constant
> Python data structures can actually be pre-allocated in the data segment
> (and I mean their object structs) . Then things like tuples of strings
> (argument lists
On 20/09/2018 15:18, Nick Coghlan wrote:
> That seems like a reasonable approach to me - it will also allow folks
> to give the changes a quick skim and provide suggestions for splitting
> it up into more easily reviewed PRs.
I already have them as individual PR's (8 Open) -
https://github.com/pyth
On Thursday, September 20, 2018, Stefan Ring wrote:
> On Tue, Sep 18, 2018 at 8:38 AM INADA Naoki
> wrote:
>
> > I think this topic should split to two topics: (1) Guard Python
> > process from Spectre/Meltdown
> > attack from other process, (2) Prohibit Python code attack other
> > processes by
On Tue, Sep 18, 2018 at 8:38 AM INADA Naoki wrote:
> I think this topic should split to two topics: (1) Guard Python
> process from Spectre/Meltdown
> attack from other process, (2) Prohibit Python code attack other
> processes by using
> Spectre/Meltdown.
(3) Guard Python from performance degra
On Tue, 18 Sep 2018 at 19:52, Michael wrote:
>
> On 17/09/2018 09:39, Michael wrote:
> > I read the discussion related to issue32374. That seems to be sure that
> > other events that could
> > cause the test to fail (i.e., the program executes successfully) are
> > caught early, and/or ignored
> >
On Wed, 19 Sep 2018 at 00:00, Michael wrote:
> On 17/09/2018 12:50, Michael wrote:
> > Dear all,
> >
> > The last two months I have spent nearly all my free time to cleanup "a
> > frustration" - from my side - the long list of failing tests for AIX
> > (there were nearly 20 when I started).
>
> ==
On Thu, 20 Sep 2018 at 20:20, Nick Coghlan wrote:
>
> On Thu, 20 Sep 2018 at 06:48, Ned Deily wrote:
> >
> > On Sep 19, 2018, at 15:08, Victor Stinner wrote:
> > > Le mardi 18 septembre 2018, Victor Stinner a écrit :
> > > > Hi Unicode and locales lovers,
> > > >
> > > > tl; dr Nick, Ned, INADA
On Thu, 20 Sep 2018 at 06:48, Ned Deily wrote:
>
> On Sep 19, 2018, at 15:08, Victor Stinner wrote:
> > Le mardi 18 septembre 2018, Victor Stinner a écrit :
> > > Hi Unicode and locales lovers,
> > >
> > > tl; dr Nick, Ned, INADA-san: I modified 3.7.1 to add a new "-X
> > > coerce_c_locale=value
On Wed, 19 Sep 2018 at 22:07, Victor Stinner wrote:
>
> > IMHO the implementation is really a secondary concern here, the main
> > question is: what is the correct behavior?
> >
> > Nick:
> >
> > * Do we agree that we need to provide a way to disable C locale
> > coercion (PEP 538) even when -E is
12 matches
Mail list logo
