RetroSearch Browse

Mon Apr 18 16:27:05 EDT 2016 · https://mail.python.org/pipermail/python-dev/2016-April/144263.html

On Tue, Apr 19, 2016 at 5:33 AM, Joseph Jevnik <joejev at gmail.com> wrote:
> I saw that there was recently a change to pep 8 to suggest adding a line
> break before a binary operator. Pep 7 suggests the opposite:
>
>> When you break a long expression at a binary operator, the operator goes
>> at the end of the previous line, e.g.:
>
>> if (type->tp_dictoffset != 0 && base->tp_dictoffset == 0 &&
>>     type->tp_dictoffset == b_size &&
>>     (size_t)t_size == b_size + sizeof(PyObject *))
>>     return 0; /* "Forgive" adding a __dict__ only */
>
> I imagine that some of the reasons for making the change in pep 8 for
> readability reasons will also
> translate to C; maybe pep 7 should also be updated.

I would agree with this. Passing it directly to python-dev as that's
where the key decision makers are.

ChrisA

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-April/144263.html below:

[Python-Dev] [Python-ideas] pep 7 line break suggestion differs from pep 8