summaryrefslogtreecommitdiff
path: root/COPYING.tools
diff options
context:
space:
mode:
authorDieter Verfaillie <dieterv@optionexplicit.be>2013-02-14 17:44:13 +0100
committerDieter Verfaillie <dieterv@optionexplicit.be>2013-04-09 23:11:55 +0200
commitf9f5452209597e0c3724ad962a68b678dbbc72cf (patch)
tree0f85f7509263bb2b824c5d77a11211745f9648ef /COPYING.tools
parent9625f52b5205f5c6f35b8300d60782a6ad6cb237 (diff)
downloadgobject-introspection-f9f5452209597e0c3724ad962a68b678dbbc72cf.tar.gz
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. https://bugzilla.gnome.org/show_bug.cgi?id=697614
Diffstat (limited to 'COPYING.tools')
0 files changed, 0 insertions, 0 deletions