Re: [Python-3000] C style guide (was: C API changes?)

2006-03-22 Thread Nick Coghlan
Brett Cannon wrote: > On 3/22/06, Thomas Wouters <[EMAIL PROTECTED]> wrote: > [SNIP] >> Speaking of PEP-3007, any ideas on how different from PEP-0007 it'll be? >> tabs or four-space indents? How rigourously will it be applied? (I honestly >> don't have any problems with PEP-0007 except for its int

Re: [Python-3000] C style guide (was: C API changes?)

2006-03-22 Thread Neal Norwitz
On 3/22/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: > > I would love it if PEP 3007 standardised on 4-space indents, the same as the > standard for Python code in the standard lib. I'd love it even more if > reindent.py cleaned up C whitespace as well as Python whitespace. Wait! I thought we were

Re: [Python-3000] C style guide (was: C API changes?)

2006-03-22 Thread Guido van Rossum
On 3/22/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: > I would love it if PEP 3007 standardised on 4-space indents, the same as the > standard for Python code in the standard lib. I'd love it even more if > reindent.py cleaned up C whitespace as well as Python whitespace. These days, > getting any C

Re: [Python-3000] C style guide (was: C API changes?)

2006-03-22 Thread Tim Peters
[Brett Cannon] |>> Yes, please! I think for the Py3K codebase we should at least require >> code meet the style guide. We are all guilty of having ignored it at >> some point, I'm not :-) > ... [Nick Coghlan] > I would love it if PEP 3007 standardised on 4-space indents, the same as the > stan