This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients docs@python, eli.bendersky, eric.smith, ezio.melotti, gvanrossum, pitrou, terry.reedy, vstinner
Date 2011-06-11.01:03:13
SpamBayes Score 3.77102e-09
Marked as misclassified No
Message-id <1307754194.63.0.0256104345777.issue12188@psf.upfronthosting.co.za>
In-reply-to
Content
We have a second item for the PEP (or Guide) section (but I think I prefer in the PEP so as to have one place to look for such things.).
So I changed the title a bit.

On 6/10/2011 3:49 PM, Guido van Rossum wrote:
> On Wed, Jun 8, 2011 at 8:12 AM, Nick Coghlan<ncoghlan@gmail.com>  
>> I actually thought Brett's rationale in the checkin comment was
>> reasonable (if you get in the habit of putting constants on the left,
>> then the classic "'=' instead of '=='" typo is a compiler error
>> instead of a reassignment).

[I understand this rationale too; I forget what I actually did when I was writing C.]

> I really like consistency across the code base. I really don't like
> constant-on-the-left, and it's basically not used in the current
> codebase. Please be consistent and don't start using it.

[I suspect I did this.]
 
>> Call it a +0 in favour of letting people put constants on the left in
>> C code if they prefer it that way, so long as any given if/elif chain
>> is consistent in the style it uses.
> 
> Sorry, I give it a -1. (I'd like to be able to read the codebase still... :-)

I bet there will be more things for a new section.
History
Date User Action Args
2011-06-11 01:03:14terry.reedysetrecipients: + terry.reedy, gvanrossum, pitrou, vstinner, eric.smith, ezio.melotti, eli.bendersky, docs@python
2011-06-11 01:03:14terry.reedysetmessageid: <1307754194.63.0.0256104345777.issue12188@psf.upfronthosting.co.za>
2011-06-11 01:03:14terry.reedylinkissue12188 messages
2011-06-11 01:03:13terry.reedycreate