GNOME Bugzilla – Bug 697614
giscanner: fix string formatting tuples
Last modified: 2015-02-07 16:51:27 UTC
Created attachment 241017 [details] [review] giscanner: fix string formatting tuples During review Colin Walters mentioned: """ One thing I should probably explain is my habit of *always* passing a tuple for %. The reason is pretty simple...a long time ago I had an error handler that did: print "unexpected data: %s" % foo. And I'd changed the type of "foo" from a string to a tuple at some point. But this obviously caused "print" to fail because it was expecting multiple format strings. Basically always using tuples is safer in case you change the type of a variable to a tuple. """ This fixes violations of this rule introduced up until now.
Created attachment 241030 [details] [review] giscanner: fix string formatting tuples Forgot to add bug link to commit message...
Review of attachment 241030 [details] [review]: Yep, and thanks a lot for keeping the style consistent. Maybe I'm the only Python programmer who got bit by this, but anyways, might as well be consistent now.
(In reply to comment #2) > Yep, and thanks a lot for keeping the style consistent. Maybe I'm the only > Python programmer who got bit by this, but anyways, might as well be consistent > now. For what it's worth, I also tend to abide by this rule as well, so I'm happy to see this go by.
Comment on attachment 241030 [details] [review] giscanner: fix string formatting tuples Committed, thanks for the review!
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]