On 05/31/2012 09:43 AM, Daniel Bryan wrote:
> Here's an example based on an application that I have in production.
> It's a bit amateurish - and I'm going to mangle the language - but you
> should get the idea.
>
> This is an extract from the main script:
>
> ===
> Class Handler(Resource):
>
Here's an example based on an application that I have in production.
It's a bit amateurish - and I'm going to mangle the language - but you
should get the idea.
This is an extract from the main script:
===
Class Handler(Resource):
pass # application code goes here - HTTP request handling,
Dear All
c/q Itamar, I really appreciate your enlightment
On 05/29/2012 09:14 PM, Itamar Turner-Trauring wrote:
>
> Applications are just a *deployment* method, providing startup and
> shutdown notification; they're not really relevant to how you interact
> with dbus. See
> http://twistedmatrix.co
On Wed, May 30, 2012 at 5:24 PM, Barry Warsaw wrote:
> On May 28, 2012, at 11:22 PM, Jasper St. Pierre wrote:
>
>>Note that dbus-python (and libdbus-1, and libdbus-glib) is deprecated.
>>The recommended solution is to use GDBus.
>
> Is it? dbus-python seems like a healthy project, getting new rel
On May 28, 2012, at 11:22 PM, Jasper St. Pierre wrote:
>Note that dbus-python (and libdbus-1, and libdbus-glib) is deprecated.
>The recommended solution is to use GDBus.
Is it? dbus-python seems like a healthy project, getting new releases fairly
regularly. For example, as of 1.0, dbus-python s
On Fri, May 18, 2012 at 9:21 PM, wrote:
> On 15 May, 10:26 am, ita...@itamarst.org wrote:
>>I have a ticket open for allowing tests that look like this, where each
>>run has a new reactor instance:
>>
>>
>>def test_somethingShouldHappen(self, reactor):
>> result = []
>> reactor.listenTC
