Thank you so much Mark, Steven. This will definitely help. I really
appreciate.
On Tue, Apr 28, 2015 at 8:45 PM, Steven D'Aprano
wrote:
> On Tue, Apr 28, 2015 at 01:01:04PM +0530, Mitesh H. Budhabhatti wrote:
> > Hello Friends,
> >
> > Can you please suggest good naming conventions/guidelines
On Tue, Apr 28, 2015 at 01:01:04PM +0530, Mitesh H. Budhabhatti wrote:
> Hello Friends,
>
> Can you please suggest good naming conventions/guidelines to following
> while writing Python code? Thanks.
Most important rule of all: names should be descriptive and
understandable, not too short or cr
On 28/04/2015 08:31, Mitesh H. Budhabhatti wrote:
Hello Friends,
Can you please suggest good naming conventions/guidelines to following
while writing Python code? Thanks.
PEP 8 - Style Guide for Python Code at
https://www.python.org/dev/peps/pep-0008/
--
My fellow Pythonistas, ask not wha
Don't get me wrong, underscores have their place,
butNotInEveryVariableName.
That_was_only_slightly_less_annoying, however.
I propose a new syntax -
All methods, shall be called Jacques, or a derivative thereof (Jack, Jake etc.)
All variables, Claude.
Oh, and you could use funny little symbols
I just read your post a heck of alot easier than I read Liam's. ;-)
Jacob Schmidt
iguessthereisnooptionleftexcepttorunwordstogetherwithoutanykindofbreakatall
thatshouldannoyeveryoneequally
Kent
Liam Clarke wrote:
Just please_don't_use_underscores. They_make_my_eyes_go_funny_,
_and_code_hard_to_rea
iguessthereisnooptionleftexcepttorunwordstogetherwithoutanykindofbreakatall
thatshouldannoyeveryoneequally
Kent
Liam Clarke wrote:
Just please_don't_use_underscores.
They_make_my_eyes_go_funny_, _and_code_hard_to_read_in_my_opinion.
_u_n_d_e_r_s_c_o_r_e_s_ _a_r_e__u_g_l_y_
I got out of the ha
Just please_don't_use_underscores.
They_make_my_eyes_go_funny_, _and_code_hard_to_read_in_my_opinion.
_u_n_d_e_r_s_c_o_r_e_s_ _a_r_e__u_g_l_y_
I got out of the habit of using them really fast.
Also, __ & _ tend to have special meaning in Python (which is bad
enough as it is), so I don't use
You're my best friend. Everyone else looves camelCase, and I hate it too. It
doesn't make sense. It doesn't fit English.
It doesn't fit Spanish. It doesn't fit any other language AFAIK, so why
should a human (who uses spoken language) to computer interpreter use a
naming convention that doesn't
Terry Carroll wrote:
On Fri, 28 Jan 2005, Kent Johnson wrote:
Separating with underscores is quite common in the Python community,
actually it is the preferred spelling for library modules. So maybe you
should adopt that, just to reduce the confusion when your code does have
an encounter with the
On Fri, 28 Jan 2005, Kent Johnson wrote:
> Separating with underscores is quite common in the Python community,
> actually it is the preferred spelling for library modules. So maybe you
> should adopt that, just to reduce the confusion when your code does have
> an encounter with the outside world
Terry Carroll wrote:
On Wed, 26 Jan 2005, Sean Perry wrote:
And now, for the pedant in me. I would recommend against naming
functions with initial capital letters. In many languages, this implies
a new type (like your Water class). so CombineWater should be combineWater.
I hate hate hate hate hat
11 matches
Mail list logo
