Jens Vagelpohl wrote at 2005-7-12 21:49 +0100:
[Lennart]
If it is the majoritys agreement that this answer is the best one, and
that the refresh functionality should be looked at as something that
may or may not work purely on luck, then I'll mark it as deprecated
and up for removal in 2.10.
Jens Vagelpohl wrote at 2005-7-12 18:46 +0100:
...
Due to the nastiness Refresh has to perform under the cover even
Shane has to admit that it simply is not some make development
faster panacea.
Shane might (perhaps) admit it but I do not :-)
There is not much nastiness that Refresh does:
Victor Safronovich wrote at 2005-7-12 18:17 +0600:
My product has 'Auto refresh mode' option checked.
I changed some source code of my product, after that autorefresh have
been
occured.
And after autorefresh I got strange several errors:
...
self._store_objects(ObjectWriter(obj),
Jeremy Hylton wrote at 2005-7-11 18:37 -0700:
IIRC, the old implementation of savepoints kept a copy of the index at
the time the savepoint was taken so that you could rollback to it
multiple times. I don't think there's any way to avoid such a copy.
Maybe, we keep the original implementation (a
Lennart Regebro wrote at 2005-7-12 19:17 +0200:
...
The refresh functionality has been unstable since it became a part of
Zope core, and I have ended up not using it since it since then
I never used auto refresh but always use the manual refresh
and I am very happy with it.
Recently, I
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:
Dieter Maurer wrote:
Jens Vagelpohl wrote at 2005-7-12 18:46 +0100:
...
Due to the nastiness Refresh has to perform under the cover even
Shane has to admit that it simply is not some make development
faster panacea.
Shane might (perhaps) admit it but I do not :-)
There is not much
On Thu, Jul 14, 2005 at 06:01:26PM -0400, Jim Fulton wrote:
| When it fails, it does so in subtle ways that cause people
| to lose lots of time.
Usually when it fails I just restart. I wouldn't consider that losing
lots of time comparing restarting now and then to restarting
constantly.
--
[Jeremy Hylton]
IIRC, the old implementation of savepoints kept a copy of the index at
the time the savepoint was taken so that you could rollback to it
multiple times. I don't think there's any way to avoid such a copy.
[Dieter Maurer]
Maybe, we keep the original implementation (a savepoint
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
Jim Fulton wrote:
It also doesn't handle global data properly.
It tries to do something that Python modules were never
designed to support, which is to load them more than once.
However, given the existence of the reload() builtin, someone apparently
believed Python modules *were* designed
[Jim Fulton]
It [reload] also doesn't handle global data properly.
It tries to do something that Python modules were never designed to
support, which is to load them more than once.
[Shane Hathaway]
However, given the existence of the reload() builtin, someone apparently
believed Python
12 matches
Mail list logo
