Refresh was never much of a timesaver for me.  Pressing "ctrl-C - up
arrow - return" on the console from which I run Zope is my answer.  I
know lots of people say that this is too slow, but on my most recent
project from the time I type "runzope" to the time I see "ready to
handle requests" is

real    0m3.029s
user    0m1.857s
sys     0m0.306s

... and I can live with that.

- C

On Thu, 2005-07-14 at 23:02 +0200, Dieter Maurer wrote:
> Lennart Regebro wrote at 2005-7-12 20:22 +0200:
> > ...
> >"well, if it happens to work for you, then
> >good luck, but it is actually a piece of unsupported crap that hasn't
> >worked for years and that nobody is bothered to fix bugs in".
> 
> I have the feeling that we have an easy tendency to say such things:
> 
>   Let a bug occur in some component and then, instead (or in addition)
>   of fixing the bug, we say often: rip the component off Zope.
> 
>   That was threadened for "Version"s, and "ZClass"es and now
>   for "Refresh".
> 
> For me, "Refresh" always was a big development time saver -- I knew
> that I had to refresh with a product also all dependent products.
> Recently, I automated this refreshing of dependent products.
> This made "Refresh" behave as expected (provided the product dependancies
> are described correctly) ;-)
> 

_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev

Reply via email to