Adi Roiban

So.... the big problem with the logger is that DEBUG, WARNING, INFO (etc) are just "log levels" and not types/tags/classes. We need to find a good name for these "warnings"...

In terms of pydoctor progress / activity reporting I think that we should have 3 types of messages: * error - this is a message that will cause pydoctor to...

Then `--warnings-as-errors` could be rename to `--fail-on-violations` or `--fail-on-warnings`

At the same time, we can keep calling them `warnings` just like in Sphinx, but to not handle them as WARNING log level. Instead have special handling for them. So,...

A crazy idea. Use `@constructor` marker to let pydoctor know that a class method is a constructor. If a class has one method with `@constructor` , move the `__init__` to...

My bad... I was not talking about `@construtor` python decorator...but rather about using an epydoc marker.

I think inheritance is the only implicit way.

So... to reproduce this "issue" You got to https://docs.twistedmatrix.com/en/latest/api/twisted.trial.unittest.SynchronousTestCase.html The `successResultOf` is listed as `Inherited from _Assertions:` and if you click it, it goes to what looks like private module....

I have approved the run now. @graingert I think that you should now be owner of everything and in the future you should be able to approve the CI run...

A bunch of tests to consider ``` def testEquality(self): """ They are equal as they have the same DN and same attributes and values. """ def testHashEquality(self): """ Objects which...