Michael Hudson schrieb:
>> According to [1], all python needs to do to avoid this problem is
>> block all signals in all but the main thread;
>
> Argh, no: then people who call system() from non-main threads end up
> running subprocesses with all signals masked, which breaks other
> things in very
Nick Maclaren schrieb:
>> (coment by Arjan van de Ven):
>> | afaik the kernel only sends signals to threads that don't have them
>> blocked.
>> | If python doesn't want anyone but the main thread to get signals, it
>> should just
>> | block signals on all but the main thread and then by nature, al
On 9/12/06, Gustavo Carneiro <[EMAIL PROTECTED]> wrote:
> On 9/12/06, Adam Olsen <[EMAIL PROTECTED]> wrote:
> > My previous mention of using a *single* flag may survive corruption
> > simply because we can tolerate false positives. Signal handlers would
> > write 0x, the poll loop would ch
As many of you probably know: Subversion 1.4 has been released.
It is safe to upgrade to this version, even if the repository
server (for us svn.python.org) stays at an older version: they
can interoperate just fine.
There is one major pitfall:
Subversion 1.4 changes the format of the working cop
On 9/12/06, Gustavo Carneiro <[EMAIL PROTECTED]> wrote:
> On 9/12/06, Adam Olsen <[EMAIL PROTECTED]> wrote:
> > My previous mention of using a *single* flag may survive corruption
> > simply because we can tolerate false positives. Signal handlers would
> > write 0x, the poll loop would ch
Anthony Baxter wrote:
> Please log a bug - this is probably something suitable for fixing in 2.5.1.
> At
> the very least, if it's going to be limited to 127 characters, it should
> check that and raise a more suitable exception.
[First time sent from wrong address, sorry if this is a dupe.]
"Adam Olsen" <[EMAIL PROTECTED]> wrote:
>
> On 9/12/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > Adam Olsen wrote:
> >
> > > That brings you back to how you access the flags variable.
> >
> > The existing signal handler sets a flag, doesn't it?
> > So it couldn't be any more broken than the curr
On 9/12/06, Adam Olsen <[EMAIL PROTECTED]> wrote:
> On 9/12/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > Adam Olsen wrote:
> >
> > > That brings you back to how you access the flags variable.
> >
> > The existing signal handler sets a flag, doesn't it?
> > So it couldn't be any more broken than th
On 9/12/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Adam Olsen wrote:
>
> > That brings you back to how you access the flags variable.
>
> The existing signal handler sets a flag, doesn't it?
> So it couldn't be any more broken than the current
> implementation.
>
> If we get too paranoid about thi
