On Monday 11 July 2005 19:32, Michael Hudson wrote:
> Well, again assuming my guess is right, it's probably an OS X bug, but
> really threads vs signals issues are enormously subtle and frequently
> messed up.
I think mwh meant to say "threads vs signals is a platform-dependant
trail of misery, d
Florent Pillet <[EMAIL PROTECTED]> writes:
> On 07/07/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
>>>
>> > But with my threaded Python code, SIGINT doesn't work anymore after my
>> > binding has called tmpfile().
>>
>> Oh, threads.
>>
>> Which version of Python are you using?
>
> 2.3.5, the on
On 07/07/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
>>
> > But with my threaded Python code, SIGINT doesn't work anymore after my
> > binding has called tmpfile().
>
> Oh, threads.
>
> Which version of Python are you using?
2.3.5, the one that ships with Mac OS X 10.4. I have a 2.4.x install
Florent Pillet <[EMAIL PROTECTED]> writes:
> I discovered an issue on Mac OS X that seems to relate to signal
> handling. I have a C binding in which I call the standard tmpfile()
> function. After calling it, I can't break Python anymore with CTRL-C.
> Investigating the Darwin source code for tm
I discovered an issue on Mac OS X that seems to relate to signal
handling. I have a C binding in which I call the standard tmpfile()
function. After calling it, I can't break Python anymore with CTRL-C.
Investigating the Darwin source code for tmpfile() (and FreeBSD, they
are the same) , I found t
