Message230190
| Author |
pitrou |
| Recipients |
docs@python, evilzero, ezio.melotti, martin.panter, michael.foord, pitrou, rbcollins |
| Date |
2014年10月29日.00:16:45 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<545031EB.1020507@free.fr> |
| In-reply-to |
<1414538570.07.0.119124123657.issue22153@psf.upfronthosting.co.za> |
| Content |
Le 29/10/2014 00:22, Martin Panter a écrit :
>
> Martin Panter added the comment:
>
> Removing stuff from the documentation would make it hard to
> understand
what existing code means that uses runTest(). Isn’t this a case where
you would add a big red "Deprecated since version . . ." warning
instead? Maybe a comprimise would be to "hide" its documentation away in
a separate deprecated section or something.
Well, I wasn't proposing a deprecation (although that can be done as
well, if we want). I was proposing that this detail be hidden. I don't
know if it would make existing software harder to understand. I don't
think I've ever seen an actively-maintained project that used runTest().
The simple way to hide it would be to stop documenting the TestCase
constructor and its signature. You aren't supposed to instantiate
TestCase yourself. |
|