As a quick fix,
class QuietSite(server.Site):
"""Like a Site but quieter"""
def log(self, request):
pass
Then use QuietSite instead of server.Site
p.
On 19 Jul 2011, at 08:37, hbd666 wrote:
> I have a simple xmlrpc server written using Twisted. Every time I get a
> request to
I have a reactor which is getting busier over time and I'd like to find out
where the cycles are going. Using the profiler isn't really practical on a
server running for days, so I'd like to instrument the reactor to show me which
I/O events are taking the longest to deal with.
Should I just h
On 5 Jan 2010, at 20:48, Ken MacDonald wrote:
> Hi, we're trying to using pyinstaller to create single-directory
> distributions of our Twisted/python server on Linux. Wondering if
> anyone has accomplished this? I googled and checked the archives,
> but there seems to be no concrete inform
On 15 Dec 2009, at 18:11, Jared Gisin wrote:
> What's wrong with writing subclasses? I've never had a case where
> that wasn't sufficient. Instead of filling up your files with all
> of these empty class definitions that define the methods that
> objects should implemmnt, why not just make
On 2 Nov 2009, at 07:22, Crispin Wellington wrote:
> On Mon, 2009-11-02 at 01:12 -0500, Glyph Lefkowitz wrote:
>> On Nov 1, 2009, at 11:17 PM, Crispin Wellington wrote:
>
>>> I tried using LoopingCall, but it does not work. It only calls the
>>> scheduler once. I think this has to do with the fac
On 7 Oct 2009, at 20:30, Paul Thomas wrote:
> Is there any way to do something like "yield sleep(10)" inside an
> @inlineCallbacks method?
I realise I can do this:
def sleep(seconds):
d = defer.Deferred()
reactor.callLater(seconds, d.callback, seconds)
return d
Is there any way to do something like "yield sleep(10)" inside an
@inlineCallbacks method?
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
On 2 Jul 2009, at 23:50, Mikhail wrote:
In my example I should have written
run(application)
instead of
run(...)
Then the difference would be more apparent. Namely, in my 'wrapper'
it is explicit what application will be run and where all the services
came from, your 'wrapper' is jus
I'm using SelectReactor on Linux for a system that spawns a lot of sub-
processes. I'm finding that there are some cases where a signal to the
twistd process doesn't reap the children and I think it's because the
SIGINT handler defers the shutdown but doesn't prevent spawnProcess()
from work
