Nice improvement. Just a couple of minor cleanup suggestions.
On Sat, Jan 12, 2013 at 9:09 AM, brett.cannon
wrote:
> +else:
> +# To prevent having to make all messages have a conditional name.
> +name = 'bytecode'
For consistency with other default/implied names, I suggest wr
Am 11.01.2013 18:19, schrieb Andrea Griffini:
> On Fri, Jan 11, 2013 at 5:08 PM, Christian Heimes
> wrote:
>> It has more issues. Coverity has sent me some complains, see attachment.
>
> The second complaint seems a false positive; if self->extra is null
> then children is set to 0 and following
On Thu, Jan 10, 2013 at 10:09 PM, Nick Coghlan wrote:
> On Fri, Jan 11, 2013 at 2:57 PM, wrote:
> > results for aef7db0d3893 on branch "default"
> >
> >
> > test_dbm leaked [2, 0, 0] references, sum=2
> > test_dbm leaked [2, 2, 1] memory blocks, sum=
On Fri, Jan 11, 2013 at 5:08 PM, Christian Heimes wrote:
> It has more issues. Coverity has sent me some complains, see attachment.
The second complaint seems a false positive; if self->extra is null
then children is set to 0 and following code is not executed.
___
This seems to have caused the Windows buildbots to fail.
On Fri, Jan 11, 2013 at 5:40 AM, serhiy.storchaka
wrote:
> http://hg.python.org/cpython/rev/8452c23139c6
> changeset: 81407:8452c23139c6
> parent: 81399:5ec8daab477a
> parent: 81406:01df1f7841b2
> user:Serhiy Storchaka
ACTIVITY SUMMARY (2013-01-04 - 2013-01-11)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open3825 ( +8)
closed 24888 (+65)
total 28713 (+73)
Open issues wit
> *Lots* of applications make use of POSIX semantics for fork() / exec().
This doesn't mean much. We're talking about inheritance of FDs > 2
upon exec, which is a very limited subset of "POSIX semantics for
fork() / exec()".
I personally think that there's been enough feedback to show that we
sho
Am 11.01.2013 07:09, schrieb Nick Coghlan:
> On Fri, Jan 11, 2013 at 2:57 PM, wrote:
>> results for aef7db0d3893 on branch "default"
>>
>>
>> test_dbm leaked [2, 0, 0] references, sum=2
>> test_dbm leaked [2, 2, 1] memory blocks, sum=5
>
> Hmm, I'm st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2013 02:55 PM, Charles-François Natali wrote:
> Indeed, it should be really rare.
*Lots* of applications make use of POSIX semantics for fork() / exec().
> There are far more programs that are bitten by FD inheritance upon
> exec than prog
On Jan 11, 2013, at 06:25 PM, Ben Leslie wrote:
>Python is not UNIX, but I think if you are directly using the POSIX
>interfaces they should work (more or less) the same way the would if you were
>writing a C program. (Some of us still use Python to prototype things that
>will later be converted
On Fri, Jan 11, 2013 at 8:37 AM, R. David Murray wrote:
> On Fri, 11 Jan 2013 08:11:00 +0100, Antoine Pitrou
> wrote:
>> On Fri, 11 Jan 2013 04:20:21 +0100 (CET)
>> ezio.melotti wrote:
>> >
>> > diff --git a/Lib/test/test_crypt.py b/Lib/test/test_crypt.py
>> > --- a/Lib/test/test_crypt.py
>> >
On Fri, 11 Jan 2013 08:11:00 +0100, Antoine Pitrou wrote:
> On Fri, 11 Jan 2013 04:20:21 +0100 (CET)
> ezio.melotti wrote:
> >
> > diff --git a/Lib/test/test_crypt.py b/Lib/test/test_crypt.py
> > --- a/Lib/test/test_crypt.py
> > +++ b/Lib/test/test_crypt.py
> > @@ -1,7 +1,11 @@
> > from test im
On 1/11/2013 2:25 AM, Ben Leslie wrote:
Python is not UNIX, but I think if you are directly using the POSIX
interfaces they should
work (more or less) the same way the would if you were writing a C
program. (Some of us
still use Python to prototype things that will later be converted to C!).
I
13 matches
Mail list logo
