[issue12188] PEP 7 (or guide) add C style policies and explanation

[anthony shaw]

anthony shaw  added the comment:

Hi,

This discussion came to a stop, but it doesn't seem conclusive.

PEP discussions are now in GitHub on https://github.com/python/peps/issues so 
I'm going to close this BPO issue.

There is no additional section in PEP 7 for this level of detail, there is also 
no tooling in place (afaik) to retroactively apply or inspect these types of 
issues, so this would need to be discussed in the PEP issue,

--
nosy: +anthonypjshaw
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12188] PEP 7 (or guide) add C style policies and explanation

[Eli Bendersky]

Changes by Eli Bendersky eli...@gmail.com:


--
nosy:  -eli.bendersky

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12188
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12188] PEP 7 (or guide) add C style policies and explanation

[Terry J. Reedy]

Terry J. Reedy tjre...@udel.edu added the comment:

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 Coghlanncogh...@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.

--
title: PEP 7, C style: add ++ policy and explanation - PEP 7 (or guide) add C 
style policies and explanation
type: feature request - 
versions: +Python 2.7, Python 3.2, Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12188
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com