txawsteam team mailing list archive

[Duncan McGreggor <duncan@xxxxxxxxxxxxx>]

Public bug reported:

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?

** Affects: txaws
     Importance: Medium
     Assignee: Duncan McGreggor (oubiwann)
         Status: New


** Tags: cleanup

** Changed in: txaws
   Importance: Undecided => Medium

** Changed in: txaws
     Assignee: (unassigned) => Duncan McGreggor (oubiwann)

-- 
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?