method names are camelCAse

[Leo Arias]

<elopio> mterry: why are you using camel case in snapcraft ?
<mterry> elopio, is that considered bad? (I thought both it and underscores were valid python strategies)
<ogra_> sergiusens, https://code.launchpad.net/~ogra/snappy/fix-interfaces-file/+merge/264578
<elopio> mterry: well, bad is relative. But it doesn't follow pep8, so yes, it's bad :)
<elopio> https://www.python.org/dev/peps/pep-0008/#function-names
<mterry> elopio, I see that link, but the pep8 command doesn't warn about it... huh (we run that with our tests)
<mterry> elopio, also I have this giant escape clause: "mixedCase is allowed only in contexts where that's already the prevailing style (e.g. threading.py), to retain backwards compatibility."
<mterry> elopio, it's already the prevailing style in snapcraft! ;)
<mterry> elopio, well I can switch if we want to
<sergiusens> ogra_: you should probably remove that changelog line, we are building them on release
<elopio> mterry: yeah, it's all relative to which snapcraft you are talking about... :) But if the idea was to use python because more developers will find it familiar, those developers will find the use of camelCase unfamiliar.
<mterry> elopio, noted, I can put it on my TODO. My poor pinky finger...

[Barry Warsaw (barry)]

On Jul 13, 2015, at 02:39 PM, Leo Arias wrote:

><elopio> mterry: why are you using camel case in snapcraft ?
><mterry> elopio, is that considered bad? (I thought both it and underscores
>were valid python strategies)

underscore_words_please

:)