> With the defaults, I usually start out at some embarrassing negative > score, and rarely end up at better than +4. But I still thank myself > later for doing what I did.
It varies, for new code I try to maintain a +10 unless there is a good reason.(Haven't encountered a case where raising the score diminished the code -- there are a few times where I felt there was a zero sum gain though, but the tipping point was +0 for consistency) For legacy code that we are not refactoring it is much lower. I do run it quite a bit as I'm finishing up refactoring and most of the time fixing the warnings results in easier to read and maintain code. I work in a very busy shop so time is a premium -- but cleaning now means easier maintenance later. Especially when there is more than 1 programmer -- agreeing on a standard then letting pylint enforce it relieves a lot of ego pressure and makes code reviews faster. You can stick to the app logic and implementation and not get sidetracked with punctuation and grammar. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
