On 09 avril 10:03, Torsten Marek wrote: > > >> loop_break.diff > > > Emit a warning for loops that have an else clause but no break or return. > > > > > > Closes #81378 > > > > I would vote to kill the special case for return which is IMO highly > > arguable. > > I feel like the rule should be the same for all, and if one feel like it's > > more readable with the else clause anyway, he should add the pragma to > > allow > > it explicitly . > > Ok. It looks like this is already in the repository (though I'm a bit > confused wrt hg.logilab.org/review vs hg.logilab.org/master), should I > modify the old patch or create a new one to change the warning and the code?
This repository confusion should be simplified soon, stay tuned. I've pushed your original changeset. We still have room to modify message id / behaviour as I proposed until this is released. And as I said, I would vote to do so. -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42) 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
