Florian Best
Florian Best
Fixes #288 I made a proof of concept some time ago and didn't have the time yet to finish it. But it gives a impression. @prologic @Osso @kromg @justingiorgi @eriol...
``` import circuits.web.tools import argparse req = circuits.web.wrappers.Request(None, server=argparse.Namespace(port=80, host='example.com')) circuits.web.tools.validate_etags(req, circuits.web.wrappers.Response(req), autotags=True) ``` causes: ``` Traceback (most recent call last): File "", line 1, in File "/home/git/circuits/circuits/web/tools.py", line 189,...
Some exceptions cause that `circuits.web` doesn't response at all: ``` #!/usr/bin/env python from circuits import Component, Debugger, handler from circuits.web import Server from circuits.web.controllers import BaseController, expose from circuits.web.errors import...
time python2 slow.py real 0m6.487s user 0m0.360s sys 0m0.030s ``` from circuits import * class a(Event): pass class b(Event): pass class Slow(BaseComponent): @handler('started') def started(self, manager): self.iter = self.foo() self.fire(a())...
Event.stop_on_error and handler.stop_on_error is a very useful thing and should be implemented.
We should enhance the possibility to write decorators for handler-functions, as `@handler` copies meta information from the function and does `arginspect()` to check if the first argument is called `event`...
circuits could support namespace packages to allow third party components to be easier integrated. See http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages See also commit c6b73daf89ec16939425af2a48b6f3b2b897ba2b where we tried it in the past. With a little...
When waiting for a already handled event the coroutine is never entered back again and blocks forever (or until a event is thrown with the same name?). Probably the following...