[Twisted-Python] Re: [Twisted-commits] Document the likley consequence of non running of unit tests

[Bruce Mitchener]

Why don't we do similar for not even putting in basic doc comments when 
new API is added?

  - Bruce

moshez CVS wrote:
> Modified files:
> Twisted/doc/howto/coding-standard.html 1.10 1.11
> 
> Log message:
> Document the likley consequence of non running of unit tests
> 
> 
> ViewCVS links:
> http://twistedmatrix.com/users/jh.twistd/viewcvs/cgi/viewcvs.cgi/doc/howto/coding-standard.html.diff?r1=text&tr1=1.10&r2=text&tr2=1.11&cvsroot=Twisted
> 
> Index: Twisted/doc/howto/coding-standard.html
> diff -u Twisted/doc/howto/coding-standard.html:1.10 Twisted/doc/howto/coding-standard.html:1.11
> --- Twisted/doc/howto/coding-standard.html:1.10	Sat Sep 21 03:04:30 2002
> +++ Twisted/doc/howto/coding-standard.html	Mon Sep 23 08:43:17 2002
> @@ -45,8 +45,8 @@
>  unfortunate and unavoidable.  The acceptance tests are highly nonportable and
>  sometimes a pain to run, so this is pardonable.  Code which breaks the unit
>  tests in a way that you could have prevented by running them yourself, however,
> -may be grounds for anything from merciless taunting to revocation of cvs commit
> -privileges.</p>
> +may be grounds for anything from merciless taunting through revertion of
> +the breakage to revocation of cvs commit privileges.</p>