ANNOUNCING Tahoe, the Least-Authority File System, v1.8.0
The Tahoe-LAFS team is pleased to announce the immediate
availability of version 1.8.0 of Tahoe-LAFS, an extremely
reliable distributed storage system. Get it here:
http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.html
Tahoe-LAFS
I think that you should not put the sys.exit(1) call, after the
reactor.stop() call.
>From my very limited understanding of how Twisted reactor works, it could be
done with something like:
statusCode = 1 #or whatever
reactor.stop()
in the method that stops the reactor
and the exit call s
David Cournapeau wrote:
> Hi,
>
> I have a program run through twistd, and would like to exit with a non
> zero status code on some error. I have a callback which stops the
> reactor and then sys.exit(some_value), but twistd still seems to catch
> the SystemExit exception after calling for reactor
On 11:09 am, yperc...@gmail.com wrote:
>I think that you should not put the sys.exit(1) call, after the
>reactor.stop() call.
>> From my very limited understanding of how Twisted reactor works, it
>>could be
>done with something like:
>
>statusCode = 1 #or whatever
>reactor.stop()
>
>in th
I'd like to add my two cents here; maybe this may be valuable to someone.
I might suggest, if reasonable, to allow for running the app with or
without twistd. twistd is really handy for
profiling/debugging/daemonizing/etc., but it does lack in other areas
such as command line args and (new to
