Hi,

Is there a reason to make it optional, rather than have it enabled at all
> times?

I assumed that the bug ticket said to make it optional. Attached is the same
code except there is no option check.
Hope this one is okay.

Donovan Lee Wanhoy

On Wed, Mar 17, 2010 at 4:44 AM, Sylvain Thénault <
[email protected]> wrote:

> On 17 mars 09:28, Maarten ter Huurne wrote:
> > > All I did was:
> > > - add an option, no-docstring-overridden that when invoked
> > > --no-docstring-overridden=y, it won't check the docstring for a method
> > > that is overridden.
> >
> > Is there a reason to make it optional, rather than have it enabled at all
> > times?
>
> I agree I don't see that much cases where we could want to disable this
> behaviour.
> --
> Sylvain Thénault                               LOGILAB, Paris (France)
> Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
> Développement logiciel sur mesure:       http://www.logilab.fr/services
> CubicWeb, the semantic web framework:    http://www.cubicweb.org
>
> _______________________________________________
> Python-Projects mailing list
> [email protected]
> http://lists.logilab.org/mailman/listinfo/python-projects
>

Attachment: C0111.diff
Description: Binary data

_______________________________________________
Python-Projects mailing list
[email protected]
http://lists.logilab.org/mailman/listinfo/python-projects

Reply via email to