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 pitrou
Recipients giampaolo.rodola, pitrou, rosslagerwall, sdaoden
Date 2011-03-01.13:40:16
SpamBayes Score 9.3271535e-07
Marked as misclassified No
Message-id <1298986813.3709.3.camel@localhost.localdomain>
In-reply-to <20110301132320.GB89055@sherwood.local>
Content
> 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.
History
Date User Action Args
2011-03-01 13:40:32pitrousetrecipients: + pitrou, giampaolo.rodola, rosslagerwall, sdaoden
2011-03-01 13:40:16pitroulinkissue11351 messages
2011-03-01 13:40:16pitroucreate