Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!lightspeed!lightspeed.eweka.nl!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'python.': 0.02; 'scripts': 0.03; 'conventions': 0.07; 'already.': 0.09; 'lawrence': 0.09; 'part,': 0.09; 'pep': 0.09; 'subject:string': 0.09; 'python': 0.11; 'mess,': 0.16; 'naming': 0.16; 'subject:library': 0.16; 'url:pep-0008': 0.16; 'url:peps': 0.16; 'sat,': 0.16; 'language': 0.16; 'wrote:': 0.18; 'library': 0.18; 'bit': 0.19; "python's": 0.19; 'programming': 0.22; 'header:User-Agent:1': 0.23; 'certainly': 0.24; 'from:addr:chris': 0.24; 'received:comcast.net': 0.24; 'url:dev': 0.24; "haven't": 0.24; 'header:In-Reply-To:1': 0.27; 'function': 0.29; 'chris': 0.29; 'am,': 0.29; "i'm": 0.30; 'code': 0.31; 'url:python': 0.33; 'development.': 0.33; 'style': 0.33; '"the': 0.34; 'subject:the': 0.34; 'but': 0.35; 'consistent': 0.36; "i'll": 0.36; 'subject:?': 0.36; 'url:org': 0.36; 'should': 0.36; 'problems': 0.38; 'to:addr :python-list': 0.38; 'pm,': 0.38; 'bad': 0.39; 'to:addr:python.org': 0.39; 'changed': 0.39; 'how': 0.40; 'read': 0.60; 'ian': 0.60; 'solve': 0.60; 'most': 0.60; 'skip:n 10': 0.64; 'love': 0.65; 'here': 0.66; 'jul': 0.74; 'received:199': 0.74 Date: Sat, 19 Jul 2014 12:43:24 -0700 From: "C.D. Reimer" User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: python-list@python.org Subject: Re: What's the proper style for a library string function? References: <53CAAD27.9010207@cdreimer.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 25 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1405799051 news.xs4all.nl 2870 [2001:888:2000:d::a6]:43383 X-Complaints-To: abuse@xs4all.nl X-Received-Bytes: 4040 X-Received-Body-CRC: 541474705 Xref: csiph.com comp.lang.python:74832 On 7/19/2014 11:56 AM, Ian Kelly wrote: > On Sat, Jul 19, 2014 at 12:24 PM, Mark Lawrence wrote: > > > Also notice that I changed the function naming style from mixedCase to > lower_case_with_underscores. This is the style recommended for Python > by PEP 8, which you should read if you haven't already. > http://legacy.python.org/dev/peps/pep-0008/#naming-conventions I love how that section of PEP 8 begins with: "The naming conventions of Python's library are a bit of a mess, so we'll never get this completely consistent -- nevertheless, here are the currently recommended naming standards." My code is certainly in "a bit of a mess" as I'm still learning Python. Following the "Core Python Programming" book for the most part, and writing scripts to solve the problems that I'm having. I got an associate degree in computer programming but never mastered a programming language outside of web development. I'll need to unlearn all the bad habits I picked up with PHP over the years. Chris Reimer