Le Thu, 24 Oct 2013 00:38:02 +0200,
Christian Heimes a écrit :
> Am 23.10.2013 23:37, schrieb Charles-François Natali:
> > Hi,
> >
> > What's the current status of pathlib? Is it targeted for 3.4?
> >
> > It would be a really nice addition, and AFAICT it has already been
> > maturing a while on
On Tuesday, Apple released OS X 10.9 (a.k.a. Mavericks). There has already
been a lot of interest in it, in part because Apple has made it available for
free and has made it easy for users with 10.8, 10.7, and (most) 10.6 systems
to upgrade directly to 10.9. Unfortunately, there are issues wi
Am 24.10.2013 11:11, schrieb Ned Deily:
> I don't know where any other potential 2.7.6 or 3.3.3 issues stand at this
> point. But I'd like Benjamin and Georg to propose an aggressive schedule so
> we can get these fixes out there.
>
We've basically agreed to do rc releases this weekend. I do
Am 24.10.2013 11:26, schrieb Georg Brandl:
> Am 24.10.2013 11:11, schrieb Ned Deily:
>
>> I don't know where any other potential 2.7.6 or 3.3.3 issues stand at this
>> point. But I'd like Benjamin and Georg to propose an aggressive schedule so
>> we can get these fixes out there.
>>
>
> We've
2013/10/24 Christian Heimes :
> There seems to be a problem with the security fix "Re-seed OpenSSL's
> PRNG after fork":
>
> http://bugs.python.org/issue18747
> http://bugs.python.org/issue19227
Yes, Charles Francois warned us that adding a pthread_atfork() hook to
add entropy may add a deadlo
On 24 October 2013 16:05, Eric Snow wrote:
> I've had some offline discussion with Brett and Nick about PEP 451
> which has led to some meaningful clarifications in the PEP. In the
> interest of pulling further discussions back onto this
> (archived/public) list, here's an update of what we'd dis
Am 24.10.2013 13:36, schrieb Victor Stinner:
> IMO the best place to fix the bug is in OpenSSL directly: RAND_bytes()
> function of OpenSSL can detect a fork using getpid() and add more
> entropy (in the child or maybe in the parent process). OpenSSL has
> access to entropy sources and knows all mu
On 24 October 2013 18:17, Antoine Pitrou wrote:
> Le Thu, 24 Oct 2013 00:38:02 +0200,
> Christian Heimes a écrit :
>> Am 23.10.2013 23:37, schrieb Charles-François Natali:
>> > Hi,
>> >
>> > What's the current status of pathlib? Is it targeted for 3.4?
>> >
>> > It would be a really nice addition
> -Original Message-
> From: Victor Stinner [mailto:victor.stin...@gmail.com]
> Sent: 24. október 2013 01:03
> To: Kristján Valur Jónsson
> Cc: Python Dev
> Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
>
>
> The use case of get_traces() + get_object_trace()
On 24 October 2013 22:34, Kristján Valur Jónsson wrote:
> I understand your desire for things to be fast, but let me just re-iterate my
> view
> that for this kind of jobs, performance is completely secondary. Memory
> debugging and analysis is an off-line, laboratory task. In my opinion,
> per
2013/10/24 Kristján Valur Jónsson :
>> Test 1. With the Python test suite, 467,738 traces limited to 1 frame:
> ...
>> I'm surprised: it's faster than the benchmark I ran some weeks ago.
>> Maybe I optimized something? The most critical operation, taking a snapshot
>> takes half a second, so it's e
Kind of on a tangent (and I suspect I know what the answer to my
question will be), but here at work they have asked people who use
Macs not to upgrade to Mavericks until Apple fixes one or more
networking problems which make it basically unusable, especially when
connecting to our VPN. I realize y
On Oct 24, 2013, at 02:11 AM, Ned Deily wrote:
>I don't know where any other potential 2.7.6 or 3.3.3 issues stand at this
>point. But I'd like Benjamin and Georg to propose an aggressive schedule so
>we can get these fixes out there.
Does this problem affect 2.6? 2.6.9 final is scheduled for
> -Original Message-
> From: Nick Coghlan [mailto:ncogh...@gmail.com]
> Sent: 24. október 2013 12:44
> To: Kristján Valur Jónsson
> Cc: Python Dev
> Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
> Not everything is a PC that you can just add more memory to (or
On 24/10/2013 15:40, Kristján Valur Jónsson wrote:
-Original Message-
From: Nick Coghlan [mailto:ncogh...@gmail.com]
Sent: 24. október 2013 12:44
To: Kristján Valur Jónsson
Cc: Python Dev
Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
Not everything is a PC t
> When I was looking for memory leaks in the regex module I simply wrote
all of the allocations, reallocations and deallocations to a log file and
then parsed it afterwards using a Python script. Simple, but effective.
He he, it's funny because you described exactly my first implementation of
trac
2013/10/24 Kristján Valur Jónsson :
>
> Now, I would personally not truncate the stack, because I can afford the
> memory,
> but even if I would, for example, to hide a bunch of detail, I would want to
> throw away
> the _lower_ detals of the stack. It is unimportant to me to know if memory
> w
2013/10/24 Georg Brandl :
> Am 24.10.2013 11:11, schrieb Ned Deily:
>
>> I don't know where any other potential 2.7.6 or 3.3.3 issues stand at this
>> point. But I'd like Benjamin and Georg to propose an aggressive schedule so
>> we can get these fixes out there.
>>
>
> We've basically agreed to d
In article <20131024094436.230220bf@anarchist>,
Barry Warsaw wrote:
> On Oct 24, 2013, at 02:11 AM, Ned Deily wrote:
> >I don't know where any other potential 2.7.6 or 3.3.3 issues stand at this
> >point. But I'd like Benjamin and Georg to propose an aggressive schedule so
> >we can get these
On Oct 24, 2013, at 01:12 PM, Ned Deily wrote:
>Yes, this problem also affects 2.6. There are some mitigating factors. The
>support for libedit on OS X is only enabled when building for an OS X 10.5 or
>later ABI because in earlier releases, the readline emulation of libedit was
>judged too b
The diff doesn't show an addition to BENCH_GROUPS. Maybe apps?
On Thu, Oct 24, 2013 at 4:24 PM, antoine.pitrou
wrote:
> http://hg.python.org/cpython/rev/8939c0196990
> changeset: 86603:8939c0196990
> user:Antoine Pitrou
> date:Thu Oct 24 22:23:42 2013 +0200
> summary:
> Clos
On 25 Oct 2013 06:42, "Barry Warsaw" wrote:
>
> On Oct 24, 2013, at 01:12 PM, Ned Deily wrote:
>
> >Yes, this problem also affects 2.6. There are some mitigating factors.
The
> >support for libedit on OS X is only enabled when building for an OS X
10.5 or
> >later ABI because in earlier releases
On Oct 25, 2013, at 07:54 AM, Nick Coghlan wrote:
>Since the default build settings work, that sounds reasonable. Perhaps
>include a note somewhere that targeting a more recent ABI may involve
>copying the 2.7 readline.c?
I'll probably add issue 18458 to the announcement and release page. That w
Progess on the Python3 as 'standard Python' front: Yesterday, FESCO
(Fedora Steering Committee?) approved a proposal to make Python 3
(version unspecified, I presume 3.3 or 3.4) the default Python in Fedora
22 (I did not see a date anywhere).
http://lwn.net/Articles/571528/
https://fedoraproje
On 25 Oct 2013 09:02, "Terry Reedy" wrote:
>
> Progess on the Python3 as 'standard Python' front: Yesterday, FESCO
(Fedora Steering Committee?) approved a proposal to make Python 3 (version
unspecified, I presume 3.3 or 3.4) the default Python in Fedora 22 (I did
not see a date anywhere).
The cur
On Thu, Oct 24, 2013 at 12:05 AM, Eric Snow wrote:
> * Nick suggested writing a draft patch for the language reference
> changes (the import page). Such a patch will be a pretty good
> indicator of the impact of PEP 451 on the import system and should
> highlight any design flaws in the API. Thi
On Thu, Oct 24, 2013 at 6:01 AM, Nick Coghlan wrote:
> On 24 October 2013 16:05, Eric Snow wrote:
>> * I've asserted that there shouldn't be much difficulty in adjusting
>> pkgutil and other modules to work with ModuleSpec.
>
> More specifically: importlib finders will still expose the previous
>
27 matches
Mail list logo
