Tristen also voted the towards using the Twisted standard. The branch that I started last week is sponsored by Canonical, and in the Landscape team we use PEP-8, so there's more code now that uses PEP-8, so we'll go down that route.
-- Inconsistent Coding Standard Employed https://bugs.launchpad.net/bugs/413738 You received this bug notification because you are a member of txAWS Team, which is the registrant for txAWS. Status in txAWS: Twisted Amazon: New Bug description: As mentioned in a recent email to the list, the naming convention used for methods in txAWS is split between camelCase and standard PEP-8 usage. This needs to be resolved as quickly as possible, since there's a good chance we're going to start using this code at Canonical and adding more stuff to it as time goes on. The coding standard needs to be consistent across the code base.. Also, we want to make this kind of API-breaking change now, before the library is used too widely to do this easily. Grep'ing the code, it seems that the Twisted standard of camelCase is most prominently used. As this is a Twisted project and this standard already holds the majority, I propose to make the necessary changes in a new branch using the Twisted standard. Does anyone have any violent objections to this? _______________________________________________ Mailing list: https://launchpad.net/~txawsteam Post to : email@example.com Unsubscribe : https://launchpad.net/~txawsteam More help : https://help.launchpad.net/ListHelp