[openstack-dev] [Tricircle] Naming convention
joehuang at huawei.com
Tue Apr 5 01:08:13 UTC 2016
Thanks for your suggestion. When using PyCharm as the IDE, one issue is that if we use abbreviation for the word to name the function or variables, there is some PEP8 promotion that you'd better to name it in a whole word, but not abbreviation.
Chaoyi Huang ( Joe Huang )
From: Shinobu Kinjo [mailto:shinobu.kj at gmail.com]
Sent: Saturday, April 02, 2016 7:40 AM
To: joehuang; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Tricircle] Naming convention
One of examples is:
# This could become:
# If we put some comment for this, this also could become:
Function: Ensure a request has right permission to given the project.
@ctx: user context
@class: class name
Point here is, honestly not only name but also appropriate length of comment.
What do you think?
On Sat, Apr 2, 2016 at 8:20 AM, joehuang <joehuang at huawei.com> wrote:
> yes, good idea, could you point out or report a bug which are not
> good naming.
> Sent from HUAWEI AnyOffice
> 时间：2016-04-02 06:21:50
> 主题:[openstack-dev] [Tricircle] Naming convention
> Hi Team,
> Probably it's worth thinking of naming convention for classes, methods
> or whatever we define in source codes.
> Some names are lengthy and there might be no consistency. At the
> moment it's fine. But once this project gets growing, situation would
> become chaotic and could cause bugs.
> What do you think?
> shinobu at linux.com
> Life with Distributed Computational System based on OpenSource
> ____ OpenStack Development Mailing List (not for usage questions)
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
shinobu at linux.com
Life with Distributed Computational System based on OpenSource
More information about the OpenStack-dev