News for hackers. Stuff that matters.
Re:Google's Python style guide by viraptor on Thursday April 19, 2012 @05:34AM (#3862117)
I hate those. Unless you're familiar with the whole team you don't know who qznc is. Git/hg/svn blame will tell you that more precisely. Inserting your name in the comment is only slightly less annoying than people insisting to put "author"comments on top of the file (or even a function)
Re:Google's Python style guide by sp332 on Thursday April 19, 2012 @07:45AM (#3862457)
I guess you could use "git blame" to find the name and email of the person who added that line?
Re:Google's Python style guide by tonfa on Thursday April 19, 2012 @05:52AM (#3862161)
And you don't have an easy to find out who he is? Or mail him based on his username?
Re:Google's Python style guide by viraptor on Thursday April 19, 2012 @07:28AM (#3862411)
If his username matches with his email, or if he uses the it consistently - maybe. But probably he wrote that note ages ago, someone else rewrote the function since then and left the comment because the content is still valid - ie. you're contacting the wrong person.

In short: metadata which is not updated automatically is most likely not up to date, and may be not correct in general.

Re:Google's Python style guide by tonfa on Thursday April 19, 2012 @09:12AM (#3862774)
You can configure the linter to check for valid username.