Dieter Maurer wrote:
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 Versions, and ZClasses and now
for Refresh.
Well, they all don't work right, confuse people are aren't
Tim Peters wrote:
[Jim Fulton]
I agree. The right way to refresh is to detect code changes (ideally
using Linux's brand new inotify mechanism, or something similar when
inotify is not available), display a please wait message to the user,
and restart the process.
If you're changing more
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),
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.
--
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
Hello zodb developers!
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:
this error was accure almost after all autorefreshs.
1.
2005-07-12 17:44:07
On 7/12/05, Jens Vagelpohl [EMAIL PROTECTED] wrote:
On 12 Jul 2005, at 13:17, Victor Safronovich wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
If it creates problems then simply don't use it.
That's not a
On Jul 12, 2005, at 1:46 PM, Jens Vagelpohl wrote:
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
If it
On 7/12/05, Jens Vagelpohl [EMAIL PROTECTED] wrote:
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
[Victor Safronovich, having problems with auto refresh]
Victor (et alia), I think a discussion of auto-refresh would be more useful
on a Zope list -- it's not really (AFAIK) a ZODB issue.
This is what changed in ZODB, from ZODB 3.3c1's NEWS file (and no, it won't
be changed back to the way it
Imagine if somebody tried to use ZPTs, and the answer to any question
where you get errors from it is well, then don't use it? It's just
not a viable answer.
Refresh is not a core functionality like ZPT. That comparison is a
bit outlandish.
If it is the majoritys agreement that this
On 7/12/05, Jens Vagelpohl [EMAIL PROTECTED] wrote:
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.
20 matches
Mail list logo
