We're using python-mockito and it works pretty good. I've also hacked it a bit
so that it works with zope interfaces. See this post, which also contains a
link
to the bitbucket project:
http://jrydberg.me/post/10519590583/strict-mocking-with-zope-interfaces
On Feb 20, 2012, at 6:04 PM, Nicolas
On 20/02/12 20:32, Glyph wrote:
> Well, it depends on how you define a "bug". LoopingCall's internal
> state remains consistent, but if you set your clock backwards,
> LoopingCall won't fire your callback again until the system clock
> catches up to where it previously was. Any new LoopingCalls
On 11:05 am, p.may...@imperial.ac.uk wrote:
>On 20/02/12 20:32, Glyph wrote:
>>Well, it depends on how you define a "bug". LoopingCall's internal
>>state remains consistent, but if you set your clock backwards,
>>LoopingCall won't fire your callback again until the system clock
>>catches up to whe
On Tue, Feb 21, 2012 at 1:05 PM, Phil Mayers wrote:
> I realise this is tricky to solve, but I'll note it's not impossible for
> really REALLY big clock skews to happen. For example: recently we had a
> server kernel panic and need a cold reboot. The machine booted and read
> it's time from the CM
