On Fri, May 29, 2009 at 03:30:26PM -0700, Christopher Lee wrote: -> I pushed blast_minor_changes to master. Note that I converted -> test_multiblast_single() back to comparing with the multiblast results -> directly. I suspect our past implementations were both based on -> trying to avoid running the lengthy multiblast more than once. To -> make the multiblast results available in two separate test methods (as -> you wanted it), I made a separate method that keeps these results -> cached as an object attribute. Take a look at -> get_multiblast_results() if you want to see the details.
Hi Chris, the multiblast results caching wasn't working as you wanted; I've fixed it in branch blast_cache: http://github.com/ctb/pygr/commit/6dfb3931a9d9b339eb62912ef2388c757deb1199 The problem with your implementation is that a new instance of each unittest.TestCase class is created for each test, so you can't use attributes attached to instances for caching; see http://docs.python.org/library/unittest.html#unittest.TestCase """ The fixture is created and cleaned up for each test case. """ for the terse little note documenting this ;). cheers, --titus -- C. Titus Brown, c...@msu.edu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
