On Oct 13, 2014, at 6:28 PM, Angus Lees g...@inodes.org wrote:
(Context: https://review.openstack.org/#/c/117418/)
I'm looking for some rough consensus on what naming conventions we want for
unused variables in Neutron, and across the larger OpenStack python codebase
since there's no
On Tue, 14 Oct 2014 12:28:29 PM Angus Lees wrote:
(Context: https://review.openstack.org/#/c/117418/)
I'm looking for some rough consensus on what naming conventions we want for
unused variables in Neutron, and across the larger OpenStack python codebase
since there's no reason for Neutron
One cannot simply prevent bike-shedding by asking people to do it up front
on the mailing list.
You'll have to wait until review time like everyone else. ;-)
On Tue, Oct 14, 2014 at 6:04 PM, Angus Lees g...@inodes.org wrote:
On Tue, 14 Oct 2014 12:28:29 PM Angus Lees wrote:
(Context:
(Context: https://review.openstack.org/#/c/117418/)
I'm looking for some rough consensus on what naming conventions we want for
unused variables in Neutron, and across the larger OpenStack python codebase
since there's no reason for Neutron to innovate here.
As far as I can see, there are two
On 14 October 2014 14:28, Angus Lees g...@inodes.org wrote:
(Context: https://review.openstack.org/#/c/117418/)
I'm looking for some rough consensus on what naming conventions we want for
unused variables in Neutron, and across the larger OpenStack python codebase
since there's no reason for
+1 for readable, well-documented code /bikeshed
On Mon, Oct 13, 2014 at 8:28 PM, Angus Lees g...@inodes.org wrote:
(Context: https://review.openstack.org/#/c/117418/)
I'm looking for some rough consensus on what naming conventions we want for
unused variables in Neutron, and across the
