Just have the class derive from ``Object``:

```python
>>> class foo:
...   def __init__(self):
...     super(foo, self).__init__()
...
>>> foo()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 3, in __init__
TypeError: must be type, not classobj
>>> class foo(object):
...   def __init__(self):
...     super(foo, self).__init__()
...
>>> foo()
<__main__.foo object at 0x105a54550>
```


On Sun, Nov 24, 2013 at 2:08 PM, ebolyen <notifications@github.com> wrote:

> In pyqi/core/interfaces/HTMLInterface/__init__.py:
>
> > +                            cmd_cfg.inputs, cmd_cfg.outputs,
> > +                            cmd_cfg.__version__)
> > +    cmd_obj = cmd_class()
> > +    #The interface needs to know what command it is
> > +    cmd_obj._set_command(cmd)
> > +    return cmd_obj
> > +
> > +def HTMLInterfaceHTTPHandler_factory(module):
> > +    """Return a subclassed BaseHTTPRequestHandler with module in scope."""
> > +
> > +    module_commands = get_command_names(module)
> > +
> > +    class HTMLInterfaceHTTPHandler(BaseHTTPRequestHandler):
> > +        """Handle incoming HTTP requests"""
> > +
> > +        _unrouted = True;
>
> Corrected at great pain. Apparently not all Python classes have super
> available to them
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bipy/pyqi/pull/203/files#r7880249>
> .
>