Greetings, > I'd like to see the tg code base be able to pylint out well > too. However, it's going to take core support and someone committing > the changes for it to happen. TurboGears then might be the first OSS project that adapted a official coding style after its 1.0 release :-)
> Do you use the standard pylint config or do you make some > modifications? I try to stick to the standard config myself. Hm, mostly. The following is a small script that I placed in the root dir of my tg application and that I call before every svn co: #!/bin/bash FILES=`find . -name "*.py"` pylint --reports=n --disable-msg=E1101,E0602,W0232,W0401,W0611,R0201 \ --max-public-methods=30 --min-public-methods=0 --include-ids=y \ --indent=$'\t' --class-rgx='([A-Z_][a-zA-Z0-9]+)|(sqlmeta)$' \ --no-docstring-rgx='(__.*__)|(sqlmeta)|(_[gs]et_.*)' \ $FILES so I overwrite some of pylints defaults, but I can justify each of them :-) mfg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
