Re: [python-win32] Request for comments - the spaces issue

2008-05-25 Thread Mark Hammond
In general, I *try* and stick to the Python Style Guide (http://www.python.org/dev/peps/pep-0008/), particularly for new code. This makes it easier to contribute code to Python itself, and a number of other projects (eg bzr) have a policy that requires contributed code conform (and indeed, they

Re: [python-win32] Request for comments

2008-05-25 Thread James Matthews
Great site. I like the idea and am going to start posting some code.. On Sat, May 24, 2008 at 9:12 PM, Tim Golden [EMAIL PROTECTED] wrote: bob gailer wrote: Tim Roberts wrote: bob gailer wrote: Please omit the space before ( in code. I find that very distracting. Example: print

Re: [python-win32] Request for comments - the spaces issue

2008-05-25 Thread bob gailer
Mark Hammond wrote: In general, I *try* and stick to the Python Style Guide (http://www.python.org/dev/peps/pep-0008/) Interesting. I don't like the idea of 2 spaces after a period. Internet research on this topic seems to favor one space. I notice when a PEP is set in monospace there are 2

Re: [python-win32] Request for comments - the spaces issue [SEC=PERSONAL]

2008-05-25 Thread Andrew MacIntyre
Interesting. I don't like the idea of 2 spaces after a period. Internet research on this topic seems to favor one space. I notice when a PEP is set in monospace there are 2 spaces after periods, otherwise 1 space. That seems inconsistent. It's not as inconsistent as might seem, as the two

Re: [python-win32] Request for comments - the spaces issue

2008-05-25 Thread Tim Golden
bob gailer wrote: Mark Hammond wrote: In general, I *try* and stick to the Python Style Guide (http://www.python.org/dev/peps/pep-0008/) Interesting. I don't like the idea of 2 spaces after a period. Internet research on this topic seems to favor one space. As it happens I'm with you on