<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD>
<BODY><!--ppd1000034-->
<DIV dir=ltr align=left><SPAN class=380161418-28052008><FONT face=Arial
color=#0000ff size=2>I think there are perhaps billions of people who get down
on their knees every day and pray to whatever god they believe in that they had
such problems as a space between a function name and a parenthesis. For
crying out loud, it's a simple search/replace at *worst* to change this to be
however you want it.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> python-win32-bounces@python.org
[mailto:python-win32-bounces@python.org] <B>On Behalf Of </B>Vernon
Cole<BR><B>Sent:</B> Wednesday, May 28, 2008 1:56 PM<BR><B>To:</B> Python-Win32
List<BR><B>Subject:</B> Re: [python-win32] Request for comments - the spaces
issue<BR></FONT><BR></DIV>
<DIV></DIV>Tim:<BR> I think you missed my point...<BR>As you say, the PEP8
style guide "is a starting point for new Python coders."<BR>That is precisely
why it ought to be followed in sample code.<BR><BR>I normally format my function
calls exactly the way you do, and I do so in open source code which I contribute
to the community. That is not EXAMPLE code which also works, it is working code
which might be used as an example: a subtle but important difference.<BR>--<BR>
<DIV class=gmail_quote>Vernon Cole<BR><BR>On Wed, May 28, 2008 at 10:46 AM, Tim
Roberts <<A href="mailto:timr@probo.com">timr@probo.com</A>> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV class=Ih2E3d>Vernon Cole wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Let's
not loose track of the thread here.<BR>The question was whether there should
be a space between the function name and the leading parenthesis,
as:<BR> my_function (arg)<BR>vs:<BR> my_function(arg)<BR><BR>PEP8
clearly requires the latter.<BR></BLOCKQUOTE><BR></DIV>PEP8 is a coding
standard document for the Python standard library. Nothing more.
It is not a mandate for all Python code. I disagree with several
of the conventions in PEP8, although if I ever submit anything to the standard
library, I will reformat it to match.<BR><BR>The key lesson in that PEP is
that you should stick to SOME standard. It need not be the same standard
used by others.
<DIV class=Ih2E3d><BR><BR><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">IMHO
any published example code, which is what we are talking about here, should
follow the PEP8 style guide.<BR></BLOCKQUOTE><BR></DIV>No, that's going WAY
too far. It is a mandate for the standard library, and it is a starting
point for new Python coders.
<DIV class=Ih2E3d><BR><BR><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">(Besides
which I personally REALLY hate the extra space.)<BR></BLOCKQUOTE><BR></DIV>You
are entitled to do so. I don't like it either, but I will certainly
defend TJG's right to write his code using his own standards. I,
personally, like Camel-cased names with an extra space inside the parentheses,
both of which are discouraged by PEP8:<BR><BR> obj = myFunction( one,
two )
<DIV class=Ih2E3d><BR><BR>-- <BR>Tim Roberts, <A href="mailto:timr@probo.com"
target=_blank>timr@probo.com</A><BR>Providenza & Boekelheide,
Inc.<BR><BR>_______________________________________________<BR></DIV>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>python-win32 mailing list<BR><A
href="mailto:python-win32@python.org"
target=_blank>python-win32@python.org</A><BR><A
href="http://mail.python.org/mailman/listinfo/python-win32"
target=_blank>http://mail.python.org/mailman/listinfo/python-win32</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR><BR><BR><P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN style="FONT-SIZE: 10pt"><FONT size=1><FONT color=navy><FONT face=Arial>DISCLAIMER:<BR>This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and<BR>may contain legally privileged and/or confidential information. If you are not the intended recipient<BR>of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and<BR>any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify<BR>me and permanently delete the original and any copy of any e-mail and any printout thereof.<BR>E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept<BR>liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission.<BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></FONT></FONT></SPAN></P><P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN style="FONT-SIZE: 10pt"><FONT size=1><FONT color=navy><FONT face=Arial>NOTICE REGARDING PRIVACY AND CONFIDENTIALITY<BR>Direct Edge ECN LLC may, at its discretion, monitor and review the content of all e-mail communications.<o:p></o:p></FONT></FONT></FONT></SPAN></P><P><SPAN style="FONT-SIZE: 10pt; COLOR: navy"><A href="http://www.directedge.com/"><FONT face=Arial color=navy size=1>www.directedge.com</FONT></A></SPAN></P></BODY></HTML>