[issue18041] mention issues with code churn in the devguide

Changes by Brett Cannon : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue18041] mention issues with code churn in the devguide

Carol Willing added the comment: https://bugs.python.org/issue23320 provides more recent input on reflow of paragraphs. This newer issue should be consulted when creating a patch for this issue. Ideally, both issues should be able to be closed with the same patch. -- nosy: +willingc

[issue18041] mention issues with code churn in the devguide

Ezio Melotti added the comment: I’ve actually seen two contrary kinds of advice and the best approach is most of the times something in between. Doing minor cleanups while touching the code is fine, but if most of the changes are cleanups then it gets distracting. In that case it's better

[issue18041] mention issues with code churn in the devguide

Martin v. Löwis added the comment: What does churn mean? -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18041 ___ ___

[issue18041] mention issues with code churn in the devguide

Éric Araujo added the comment: Moving things around. -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18041 ___ ___

[issue18041] mention issues with code churn in the devguide

Éric Araujo added the comment: Tshepang is referring to cases where a patch changes one line but affects ten other lines because a paragraph was rewrapped, modernizing code, updating tests to use latest helpers, etc. I’ve actually seen two contrary kinds of advice: do cleanups when you touch

[issue18041] mention issues with code churn in the devguide

New submission from Tshepang Lekhonkhobe: I've seen complaints about code churn a few times, example: http://bugs.python.org/issue16510#msg175956. Would be nice if this was documented in the devguide. -- components: Devguide messages: 189844 nosy: ezio.melotti, tshepang priority: