A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2009-January/084964.html below:

[Python-Dev] Fixing incorrect indentations in C files (Decoder functions accept str in py3k)

[Python-Dev] Fixing incorrect indentations in C files (Decoder functions accept str in py3k) [Python-Dev] Fixing incorrect indentations in C files (Decoder functions accept str in py3k)Benjamin Peterson benjamin at python.org
Fri Jan 9 02:31:12 CET 2009
On Thu, Jan 8, 2009 at 2:52 PM, Brett Cannon <brett at python.org> wrote:
> On Thu, Jan 8, 2009 at 12:43, Nick Coghlan <ncoghlan at gmail.com> wrote:
>>
>> Even if we do adopt such a rule, C patches posted to the tracker should
>> still try to avoid including pure whitespace changes though - leaving
>> the whitespace changes in the patch tends to lead to patches that look
>> like "remove function body, add different function body" when only a
>> couple of lines have actually had significant changes.
>>
>
> That's fine with me. Correcting whitespace can be considered a committer's job.

Maybe a rule could be added to Tools/scripts/patchcheck.py?



-- 
Regards,
Benjamin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4