This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients LambertDW, Retro, georg.brandl, gvanrossum, loewis, rhettinger
Date 2008-12-13.16:07:32
SpamBayes Score 1.9258485e-07
Marked as misclassified No
Message-id <1229184513.65.0.380897833727.issue4649@psf.upfronthosting.co.za>
In-reply-to
Content
Retro, you are blowing this way out of proportion.  Style guidelines are
not absolute rules that must be followed at all cost, and there are
always exceptions.  You need to have a lot of experience before you can
claim with certainty that a certain piece of code should or should not
be formatted according to the style guidelines.  (This is as opposed to
the syntax of the language, which is an absolute set of rules where
violations raise a SyntaxError.)

In this case, the PEP never meant to say that all arithmetic operators
have to be surrounded by spaces.  That would make just as little sense
as requiring no spaces.  The words in the PEP cannot possibly
approximate the set of heuristics I have in my mind for this purpose, 
and I don't think they have to.  When I wrote PEP 8 (or actually its
precursor), I was merely *suggesting* that certain uses of spaces look
better than others.  If you are interpreting this as requiring all
examples needing to follow the literal style guide, well, Im sorry, but
that's not how it was meant, and I am not willing to either change the
examples (the specific one you quote looks just fine to me) or to edit
the PEP to try and formulate a more complex rule.  In my experience, the
more baroque the rule the more arguments it elicits.
History
Date User Action Args
2008-12-13 16:08:33gvanrossumsetrecipients: + gvanrossum, loewis, georg.brandl, rhettinger, LambertDW, Retro
2008-12-13 16:08:33gvanrossumsetmessageid: <1229184513.65.0.380897833727.issue4649@psf.upfronthosting.co.za>
2008-12-13 16:07:33gvanrossumlinkissue4649 messages
2008-12-13 16:07:32gvanrossumcreate