[Biopython-dev] Unit tests for deprecated modules?

[Michiel de Hoon]

I would say (a). In my opinion, deprecated means that the module is in essence no longer part of Biopython; we just keep it around to give people time to change. Also, deprecation warnings distract from real warnings and errors in the unit tests, are likely to confuse users, and give the impression that Biopython is not clean. I don't remember a case where we had to resurrect a deprecated module, so we may as well remove the unit test right away.

--Michiel


--- On Tue, 8/19/08, Peter <biopython at maubp.freeserve.co.uk> wrote:

> From: Peter <biopython at maubp.freeserve.co.uk>
> Subject: [Biopython-dev] Unit tests for deprecated modules?
> To: "BioPython-Dev Mailing List" <biopython-dev at biopython.org>
> Date: Tuesday, August 19, 2008, 6:52 AM
> Are there any strong views about when to remove unit tests
> for
> deprecated modules?  I can see two main approaches:
> 
> (a) Remove the unit test when the code is deprecated, as
> this avoids
> warning messages from the test suite.
> (b) Remove the unit test only when the deprecated code is
> actually
> removed, as continuing to test the code will catch any
> unexpected
> breakage of the deprecated code.
> 
> I lean towards (b), but wondered what other people think.
> 
> Peter
> _______________________________________________
> Biopython-dev mailing list
> Biopython-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/biopython-dev