Hello Tim Peters,
Tuesday, October 25, 2005, 7:50:49 AM, you wrote:
TP> I'm not entirely sure what you're trying to accomplish. time.sleep(x) is
TP> the _natural_ way to spell "this thread wants to yield to other threads for
TP> at least the next x wall-clock seconds". If that's what you want t
...
[Tim Peters]
>> Heh. Is there a secret agenda here, or is that line an elaborate way
>> to spell "time.sleep(random())"?
[Victor Safronovich]
>yes, this is an elaborate way :)). Do you think that use "time.sleep"
> is more correct way to freeze the thread?
I'm not entirely sure what you
Hello Tim Peters,
Friday, October 21, 2005, 11:08:28 PM, you wrote:
TP> Heh. Is there a secret agenda here, or is that line an elaborate way to
TP> spell "time.sleep(random())"?
yes, this is an elaborate way :)). Do you think that use "time.sleep" is more
correct way to freeze the thread?
Victor Safronovich wrote at 2005-10-21 14:54 +0600:
> ...
>app = Zope.bobo_application()
>try:
>self.running = True
>while self.running:
>get_transaction().begin()
>try:
>scheduler = app.unrestrictedTraverse
[Victor Safronovich]
> Hello zodb-dev!
>
> I have Zope 2.6.1 with ZODB 3.1.5 ( I know this is old versions ).
Too old ;-) ZODB 3.1.5 was released in February of 2004, was the last
release in the 3.1 line, and it would be a real pain to try to identify the
critical bugs fixed in later ZODBs that r
Hello zodb-dev!
I have Zope 2.6.1 with ZODB 3.1.5 ( I know this is old versions ).
I have scheduler in separate thread with code
class EventDispatcher( threading.Thread ):
running = False
def __init__( self, scheduler ):
self.scheduler_path = scheduler.getPhysicalPath()
t
