On 24 Jan, 07:51 pm, [email protected] wrote:
On 24 January 2015 at 19:23, <[email protected]> wrote:
On 06:45 pm, [email protected] wrote:
Hi,
Why reviewing a patch I got into this error from twistedchecker.
This is old code, just that someone it was touched by recent changes,
Also: pre-existing errors like this one should not block new development
work being done. It is *not* a requirement that a patch fix all nearby
but unrelated problems like this one.
New and changed code should conform to the standard and try not to
introduce new errors. If the "errors" being introduced are due to bugs
in a tool that reports errors, the bugs should be fixed.
Existing code *near* new or changed code can and should be left alone.
Jean-Paul
_______________________________________________
Twisted-Python mailing list
[email protected]
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
