On Feb 11, 2011, at 11:55 AM, exar...@twistedmatrix.com wrote:
> On 03:59 pm, jren...@gmail.com wrote:
>> On Fri, Feb 11, 2011 at 10:01 AM, wrote:
>>> On Python 2.5 and earlier you won't be able to get Twisted's SIGCHLD
>>> handler using signal.getsignal.
>>
>> We're also moving to python 2.6 (
On Fri, Feb 11, 2011 at 11:55 AM, wrote:
> For shutdown-type things, reactor.addSystemEventTrigger(phase,
> 'shutdown', f) might be better than getting into signal handlers (where
> phase is 'before', 'during', or 'after').
That might be a better way to go. Thanks for the tip.
Jason
--
Jaso
On Feb 11, 2011, at 8:04 AM, Stephen Waterbury wrote:
> On 02/11/2011 01:30 AM, Lucas Taylor wrote:
>> On Feb 10, 2011, at 1:24 PM, Stephen Waterbury wrote:
>>
>>> This url should really be linked either from Twisted's main page
>>> or at the very least on the "Twisted Community" page:
>>>
>>> ht
On 03:59 pm, jren...@gmail.com wrote:
>On Fri, Feb 11, 2011 at 10:01 AM, wrote:
>>On Python 2.5 and earlier you won't be able to get Twisted's SIGCHLD
>>handler using signal.getsignal.
>
>We're also moving to python 2.6 (the change is really Debian 5 to
>Debian 6).
>Should it would work in 2.6?
On Fri, Feb 11, 2011 at 10:01 AM, wrote:
> On Python 2.5 and earlier you won't be able to get Twisted's SIGCHLD
> handler using signal.getsignal.
>
We're also moving to python 2.6 (the change is really Debian 5 to Debian 6).
Should it would work in 2.6?
> What sort of things do your signal ha
On 02/11/2011 01:30 AM, Lucas Taylor wrote:
> On Feb 10, 2011, at 1:24 PM, Stephen Waterbury wrote:
>
>> This url should really be linked either from Twisted's main page
>> or at the very least on the "Twisted Community" page:
>>
>> https://launchpad.net/tx
>>
>
> It is linked from here, with a des
On 02:27 pm, jren...@gmail.com wrote:
>I'm in the process of porting code from Twisted 8.1 to 10.1 which
>needed
>some custom signal handling code. Twisted 8.1's approach to signal
>handling
>was (as far as we could tell) too monolithic, so we chose
>"installSignalHandlers=False" and wrote our o
I'm in the process of porting code from Twisted 8.1 to 10.1 which needed
some custom signal handling code. Twisted 8.1's approach to signal handling
was (as far as we could tell) too monolithic, so we chose
"installSignalHandlers=False" and wrote our own signal handling code,
installing reactor._h
