bob gailer wrote:
Tim Roberts wrote:
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
Let's not loose track of the thread here.
The question was whether there should be a space between the function name
and the leading parenthesis, as:
my_function (arg)
vs:
my_function(arg)
PEP8 clearly requires the latter.
IMHO any published example code, which is what we are talking about
Vernon Cole wrote:
Let's not loose track of the thread here.
The question was whether there should be a space between the function
name and the leading parenthesis, as:
my_function (arg)
vs:
my_function(arg)
PEP8 clearly requires the latter.
PEP8 is a coding standard document for the
Vernon Cole wrote:
Let's not loose track of the thread here.
The question was whether there should be a space between the function
name and the leading parenthesis, as:
my_function (arg)
vs:
my_function(arg)
PEP8 clearly requires the latter.
IMHO any published example code, which is what
Tim:
I think you missed my point...
As you say, the PEP8 style guide is a starting point for new Python
coders.
That is precisely why it ought to be followed in sample code.
I normally format my function calls exactly the way you do, and I do so in
open source code which I contribute to the
you want it.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vernon Cole
Sent: Wednesday, May 28, 2008 1:56 PM
To: Python-Win32 List
Subject: Re: [python-win32] Request for comments - the spaces issue
Tim:
I think you missed my point...
As you
Vernon Cole wrote:
Tim:
I think you missed my point...
As you say, the PEP8 style guide is a starting point for new Python
coders.
That is precisely why it ought to be followed in sample code.
I normally format my function calls exactly the way you do, and I do
so in open source code which
Vernon,
Tim:
I think you missed my point...
As you say, the PEP8 style guide is a starting point for new Python
coders.
That is precisely why it ought to be followed in sample code.
I normally format my function calls exactly the way you do, and I do
so in open source code which I
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.
I'm not sure where you got that.
Tim Roberts wrote:
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.
I'm not sure
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
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
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
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
[bob gailer]
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ (sValue).Value # current
print result.Properties_(sValue).Value # preferred, and how most
code I've seen looks.
[Tim Roberts]
Do you understand that this is strictly a
] Request for comments - the spaces issue
[bob gailer]
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ (sValue).Value # current
print result.Properties_(sValue).Value # preferred, and how most
code I've seen looks.
[Tim Roberts]
Do
PROTECTED] On Behalf Of Tim Golden
Sent: Saturday, May 24, 2008 4:28 AM
Cc: Python-Win32 List
Subject: Re: [python-win32] Request for comments - the spaces issue
[bob gailer]
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ (sValue).Value
Tim Golden wrote:
[snip]
Likewise I imagine there are many who find my two-spaces
indent style cluttered while I find even four and certainly any
more to be grotesquely elongated.
I also prefer the 2 space indent!
I also realize that when I wrote my previous reply I was not conscious
that
bob gailer wrote:
Tim Golden wrote:
[snip]
Likewise I imagine there are many who find my two-spaces
indent style cluttered while I find even four and certainly any
more to be grotesquely elongated.
I also prefer the 2 space indent!
I also realize that when I wrote my previous reply I was
19 matches
Mail list logo
