Antoine Pitrou <pit...@free.fr> added the comment: > Maybe Giampaolo' should at least replace these two > PyArg_ParseTupleAndKeywords() near (unpatched) line 5942, > because doing it like this is messes up (at least) vim(1) group > detection, resulting in a lot of bold red mis-brace warnings > further on?
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
