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.listenTCP(...)
> self.runReactor(reactor)
> self.
On 04:32 pm, spa...@gresille.org wrote:
> Hello,
>On 17/05/2012 02:00, Jasper St. Pierre wrote:
>>I don't understand why you can't make Django do asynchronous calls.
>>Maybe a bit more context would help.
> Once again, maybe I *cannot* make Django do asynchronous calls
>simply
>bec
Hello,
On 17/05/2012 02:00, Jasper St. Pierre wrote:
> I don't understand why you can't make Django do asynchronous calls.
> Maybe a bit more context would help.
Once again, maybe I *cannot* make Django do asynchronous calls simply
because I am not used to Twisted and asynchronous c
