Is anyone using pylint on their TG source code? If you are, what, if any, changes have you made to your rcfile?
There are some naming conventions that make pylint cry foul, given that Kevin has ruled that PEP 8 should be the standard, http://docs.turbogears.org/1.0/Contributing#coding-style - however there is some flexibility in naming and such. I was hoping that some one had already had a pylint rcfile that accounted for these with regards to TG. With the docstring party that is approaching, it might be a good idea to use a tool like pylint to automate a portion of code checking/submission process since tools like pylint can find missing docstrings, naming convention problems, unused imports, bad coding practices, etc. (I am a lazy guy and if I can get a tool to do it for me -- lucky me<g>) One final group question, does anyone else have issues with from sqlobject import * I didn't find a specific reference to it in PEP 8, general wisdom considers it bad form unless you are at the interactive prompt http://docs.python.org/tut/node8.html#SECTION008410000000000000000 -j --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
