Jeff Hinrichs - DM&T schrieb:
A valid argument, the easier a thing is to do, the more likely it is
to be done. I agree that we should go with your python script idea.
Perhaps, pylint_tg.py to reflect the turbogears bias? If you would
like to code it up we could add it (to the document and/or a link to a
download) and then perhaps in the footer of the Usage section or a
hint area, point out the --generate-rcfile method. I like that method
since I've wired the pylint --rc-file=.pylintrc %F in to my editor.
pylint always runs and if I've set up the config file it uses it,
otherwise it uses the defaults. However, that is an editor issue and
you are correct that we should focus on cmd line usage as the primary
method since it is more universal.
At the moment I use the following script:
http://paste.turbogears.org/paste/865
I used the TG naming scheme and named it pylint_$projectname.py which
fits in with
start_$projectname.py
Agreed, recommending the disabling [of W0232] in the header is a defensible
compromise that tends towards explicitness (a good thing).
Great, I will try to change the document to that.
-Jeff
ps. Will you be attending PyCon in February?
Eh, I never thought about it. But by now it's much too late I think,
getting the days of from work and the permission from my
treasurer-in-command ... But maybe next year. Or Europython. I dont
know :-)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
