On Mon, Apr 27, 2009 at 06:20:46AM -0700, Istvan Albert wrote: -> On Apr 26, 11:29?pm, "C. Titus Brown" <c...@msu.edu> wrote: -> -> > (The rationale is that we want to know the function name of the test -> > being run, so that we can identify the test & re-run it as necessary.) -> -> hey I've actually put in some time in creating nicer docstrings as I -> always thought that there is value in having a good understanding of -> what type of tests are run, what features are tested, what passes, -> and a how-to perform certain operations, you can look in the tests as -> they were docs. -> -> but this makes sense too so I restored the original behavior. -> (the reason it was hard coded is that I had a hard time justifying -> adding another tunable parameter).
fair enough ;) A good intermediate would be to print out *both*, but that would require more unittest hacking. 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 -~----------~----~----~----~------~----~------~--~---
