On 1/18/07, goff <[EMAIL PROTECTED]> wrote:
Hi, > I made a counter proposal to you in the usage section. Essentially I > wrote up how to turn your command line options into a config file > using --generate-rcfile. Still I think a that a short script (either shell or python, the later one having the advantage of doing well on windows too) might be more userfriendly. After all ./pyl[Tab][Enter] (6 key presses) is much easier to type then pyl[Tab] --rcfile=.py[Tab][Enter] (18 key presses) and less error prone. It also shares .pylintrc's advantage of being under revision control
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.
> Also, W0232 has my vote for inclusion in to the global settings. Is > that the way your are leaning on it? I'm not sure. I think that the warning is good and well and should only be disabled for Controllers and SQLObjects. But more than 90% of a projects classes are either Controllers or SQLObjects, so one could say that a global option to disable W0232 is in order. No, to sum it up I'd rather have this warning disabled in the header of a model or controller file. But Both options are valid, so I think we will come to an agreement somehow.
Agreed, recommending the disabling in the header is a defensible compromise that tends towards explicitness (a good thing).
> I really like the way you handled the opposing views on wild card imports. Thanks. My problem is that I can see the benefit in both, and when I'm in doubt I rather say so and let the user decide. > Depending on what you think about my changes to the usage section, I > think we are pretty close. What do you think? Yes, only the .pylintrc/pylint_project.py and W0232 remain, two minor issues I'd think. Best regards, mfg
-Jeff ps. Will you be attending PyCon in February? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
