Operator precedence problem
jon+usenet at unequivocal.co.uk
Mon Jun 6 11:27:47 EDT 2016
On 2016-06-06, Marko Rauhamaa <marko at pacujo.net> wrote:
> Jon Ribbens <jon+usenet at unequivocal.co.uk>:
>> On 2016-06-06, Marko Rauhamaa <marko at pacujo.net> wrote:
>>> You *can* assume other people have read the spec. Even more
>>> importantly, you can assume the Python interpreter complies with the
>> Obviously the latter is true (or at least, it's true except when it's
>> false). The former however is not true.
> Well, of course nobody knows the whole spec. However, you should write
> your code assuming they do.
That sounds like bad advice to me I'm afraid. Assume they're
moderately competent, sure. Assume they know 100% of the entire spec
in all its detail? That's an assumption that will be false pretty much
100% of the time.
>> You should put brackets around expressions when it's at all unclear
>> what the meaning is. You could think of them a bit like "active
>> comments" I suppose.
> Your code should keep noise to the minimum.
Sensible and beneficial comments aren't "noise".
More information about the Python-list