Thomas Wouters wrote:
> Your idea of making this an API called a 'fork lock' or something
> sounds good (though I think it needs a better name. PyBeforeFork &
> PyAfterFork?). The subprocess module, for example, disables garbage
> collection before forking and restores it afterwar
On 9 Sep, 2009, at 19:29, Ned Deily wrote:
Without trying to put Ronald on the spot (too much!), it would be a
good
idea to get his assessment where things stand wrt 2.6 on 10.6 before
setting a final release date.
MacOS X 10.6 support should be stable now, except for a critical issue
wit
On Sep 9, 2009, at 1:29 PM, Ned Deily wrote:
In article <11a6545d-7204-4f61-b55b-1cc77cb56...@python.org>,
Barry Warsaw wrote:
I still want to release by the 25th, but I'd be willing to move the
rc
to Monday the 21st. We're really just trying to avoid a brown bag
moment, so that should give
On Wed, Sep 9, 2009 at 20:19, Gregory P. Smith wrote:
> On Wed, Sep 9, 2009 at 9:07 AM, Thomas Wouters wrote:
> >
> >
> > On Sat, Jul 25, 2009 at 19:25, Gregory P. Smith wrote:
> >>
> >> On Thu, Jul 23, 2009 at 4:28 PM, Thomas Wouters
> wrote:
> >> >
> >> > So attached (and at http://codereview.
On Wed, Sep 9, 2009 at 11:36 AM, Thomas Wouters wrote:
>
> On Wed, Sep 9, 2009 at 20:19, Gregory P. Smith wrote:
>>
>> Take a look at http://code.google.com/p/python-atfork/ which I created
>> to address the general fork+threading with locks held causing
>> deadlocks issue with many standard libra
On Wed, Sep 9, 2009 at 9:07 AM, Thomas Wouters wrote:
>
>
> On Sat, Jul 25, 2009 at 19:25, Gregory P. Smith wrote:
>>
>> On Thu, Jul 23, 2009 at 4:28 PM, Thomas Wouters wrote:
>> >
>> > So attached (and at http://codereview.appspot.com/96125/show ) is a
>> > preliminary fix, correcting the problem
In article <11a6545d-7204-4f61-b55b-1cc77cb56...@python.org>,
Barry Warsaw wrote:
> I still want to release by the 25th, but I'd be willing to move the rc
> to Monday the 21st. We're really just trying to avoid a brown bag
> moment, so that should give us enough time to double check the rele
On Sat, Jul 25, 2009 at 19:25, Gregory P. Smith wrote:
> On Thu, Jul 23, 2009 at 4:28 PM, Thomas Wouters wrote:
> >
> > So attached (and at http://codereview.appspot.com/96125/show ) is a
> > preliminary fix, correcting the problem with os.fork(), os.forkpty() and
> > os.fork1(). This doesn't exp
On Tue, Sep 8, 2009 at 19:56, Benjamin Peterson wrote:
> 2009/9/7 Eric Pruitt :
>> Hello all,
>>
>> I have been working on adding asynchronous I/O to the Python
>> subprocess module as part of my Google Summer of Code project. Now
>> that I have finished documenting and pruning the code, I present
On Sep 9, 2009, at 9:29 AM, Nick Coghlan wrote:
Barry Warsaw wrote:
I had previously wanted to release Python 2.6.3 over the summer,
but for
various personal reasons, the summer was just too insane. I'd like
to
reschedule a 2.6.3 release, shooting for final release on 25-
September.
We s
Barry Warsaw wrote:
> I had previously wanted to release Python 2.6.3 over the summer, but for
> various personal reasons, the summer was just too insane. I'd like to
> reschedule a 2.6.3 release, shooting for final release on 25-September.
>
> We should probably do a release candidate, so I'd li
I had previously wanted to release Python 2.6.3 over the summer, but
for various personal reasons, the summer was just too insane. I'd
like to reschedule a 2.6.3 release, shooting for final release on 25-
September.
We should probably do a release candidate, so I'd like to make that on
23
12 matches
Mail list logo
