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.
________________________________ 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 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 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. -- Vernon Cole On Wed, May 28, 2008 at 10:46 AM, Tim Roberts <[EMAIL PROTECTED]> wrote: 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 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. The key lesson in that PEP is that you should stick to SOME standard. It need not be the same standard used by others. IMHO any published example code, which is what we are talking about here, should follow the PEP8 style guide. 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. (Besides which I personally REALLY hate the extra space.) 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: obj = myFunction( one, two ) -- Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc. _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32 DISCLAIMER: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Direct Edge ECN LLC may, at its discretion, monitor and review the content of all e-mail communications. www.directedge.com
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
