Steffen Daode Nurpmeso <sdao...@googlemail.com> added the comment:
But, dear Antoine, i don't know *any* editor that is capable to
handle the following code correctly:
#ifdef __APPLE__
if (!PyArg_ParseTupleAndKeywords(args, kwdict, "iiO&O&|OOi:sendfile",
keywords, &out, &in, _parse_off_t, &offset, _parse_off_t, &sbytes,
#else
if (!PyArg_ParseTupleAndKeywords(args, kwdict, "iiO&n|OOi:sendfile",
keywords, &out, &in, _parse_off_t, &offset, &len,
#endif
&headers, &trailers, &flags))
> Antoine Pitrou <pit...@free.fr> added the comment:
>
> Problem is, each developer has his/her own preferences and editor
> settings, so if we start reformatting with each commit, the history of a
> piece of code becomes very difficult to read.
>
> I would simply suggest that you disable these vim settings, or at least
> tweak them so that they don't apply automatically when you edit existing
> code.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11351>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
