Am 01.03.2010 01:23 schrieb Christoph Zwerschke:
I'm pretty sure it has something to do with the fact that TG 1.5 uses peak.rules which seems to confuse coverage.
Update: Ned confirmed that this is the case. You can pass a --timid option to coverage which makes it run slower, but works with peak. It seems by running a 32bit coverage on my 64bit system it resorted to using this --timid method, so that explains why it worked for me in this setting. It also shows the two failing tests I mentioned above. I'm currently trying to evaluate whether these failures with the --timid method can be fixed in coverage and how to set --timid with nose other than via a .coveragerc config file.
-- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
