Robert Collins writes:
> I'd probably shut that warning up using the warnings module API rather
> than weaking the test more broadly.
Might be the best thing.
> Also - track down and file a bug on the leak source.
How *do* you track these down? The warning doesn't say where the file
was opened
I'd probably shut that warning up using the warnings module API rather
than weaking the test more broadly. Also - track down and file a bug
on the leak source.
Brian May writes:
> ==
> FAIL: test_discovery_with_broken (djcelery.tests.test_discovery.TestDiscovery)
> --
> Traceback (most recent call last):
> File
> "/h
3 matches
Mail list logo
