External Methods - Weirdness between two installations of Zope
So we have a "test" and "production" installation of Zope 2.6. I'm experiencing some very interesting wierdness with external methods on the two systems. Now, I didn't play an integral role to the setup of these services, so the answer may be a simple configuration option I'm unawares of and my tech people are too ambivalent to care about Anyway, I've developed a small application on the test environment that has many external methods. I would often be editing the scripts in a telnet session and then reloading pages to see the new results. No problem. I copy over the product to the production environment - I exported over the zope objects and copied the .py file to the other Extensions folder - and there are a few small bugs to work out. But on THIS instance of zope, changes to the external method are not reflected unless I go into the method object in the ZMI and click "save changes". This stikes me as very unusual. Any advice? Edward Pollard Web Programmer Guy, University of Lethbridge
Dear Edward,
So we have a "test" and "production" installation of Zope 2.6. I'm experiencing some very interesting wierdness with external methods on the two systems. Now, I didn't play an integral role to the setup of these services, so the answer may be a simple configuration option I'm unawares of and my tech people are too ambivalent to care about
Anyway, I've developed a small application on the test environment that has many external methods. I would often be editing the scripts in a telnet session and then reloading pages to see the new results. No problem.
I copy over the product to the production environment - I exported over the zope objects and copied the .py file to the other Extensions folder - and there are a few small bugs to work out. But on THIS instance of zope, changes to the external method are not reflected unless I go into the method object in the ZMI and click "save changes".
This stikes me as very unusual. Any advice?
It sounds like your development installation is running in debug mode, but your production one isn't. Which is pretty sensible. The development Zope will have either been started with the -D option or with the Z_DEBUG_MODE environment variable set (do a "python z2.py --help" or read doc/DEBUGGING.txt for more info). One of the effects of debug mode is that Zope reloads external methods automatically if they've changed on the filesystem. For other effects, see: http://www.zope.org/Members/klm/debuggingzope Cheers, Ian -- Dr Ian Sealy Internet Development Institute for Learning and Research Technology University of Bristol
On Fri, Jan 10, 2003 at 12:42:43AM +0000, Ian Sealy wrote:
One of the effects of debug mode is that Zope reloads external methods automatically if they've changed on the filesystem. For other effects, see:
<rant mode="tangent"> Is it just me, or is anyone else really irritated by how many things are toggled by Z_DEBUG_MODE? For example, I want my production site to not display tracebacks to users, but I *don't* want it to detach from the terminal - I agree with the author of daemontools that a daemon which insists on running in the background is broken. If I wanted to run it in the background, **** I would put it in the background. **** I looked into patching z2.py to add some command line switches (e.g. --html-tracebacks, --foreground, --auto-refresh ...) and then the current -D could just invoke a combination of other switches. But it looks like a pretty involved job to patch zope to separate out all the stuff that's lumped in as "debugging". It looks to me like changes would have to be made all over the place. Grrrr. </rant> -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's MISUNDERSTOOD SWITZERLAND UNDERWEAR INSPECTOR! (courtesy of isometric.spaceninja.com)
The place to add these kinds of features is in Zope 2.7. It is a fairly big job to subdivide them but possible. You may want to wait until the installer stuff is merged to do this (which may be a few weeks). On Thu, 2003-01-09 at 20:42, Paul Winkler wrote:
On Fri, Jan 10, 2003 at 12:42:43AM +0000, Ian Sealy wrote:
One of the effects of debug mode is that Zope reloads external methods automatically if they've changed on the filesystem. For other effects, see:
<rant mode="tangent">
Is it just me, or is anyone else really irritated by how many things are toggled by Z_DEBUG_MODE?
For example, I want my production site to not display tracebacks to users, but I *don't* want it to detach from the terminal - I agree with the author of daemontools that a daemon which insists on running in the background is broken. If I wanted to run it in the background, **** I would put it in the background. ****
I looked into patching z2.py to add some command line switches (e.g. --html-tracebacks, --foreground, --auto-refresh ...) and then the current -D could just invoke a combination of other switches.
But it looks like a pretty involved job to patch zope to separate out all the stuff that's lumped in as "debugging". It looks to me like changes would have to be made all over the place. Grrrr.
</rant> -- Chris McDonough <chrism@zope.com> Zope Corporation
On Thu, Jan 09, 2003 at 08:53:50PM -0500, Chris McDonough wrote:
The place to add these kinds of features is in Zope 2.7. It is a fairly big job to subdivide them but possible. You may want to wait until the installer stuff is merged to do this (which may be a few weeks).
I would be happy to do some work on it if i can ever get out from under this endless, PHB-driven mess of fonts & colors* which is making me so grumpy. The hard part will probably be just finding all the things that need to be changed. I spent about 20 minutes looking for this stuff a while ago and punted. Hopefully the folks over on zope-dev will be able to help. * a truly great quote: http://www.zopezen.org/Members/slinkp/Quote.2003-01-09.0238 --PW Paul Winkler http://www.slinkp.com Look! Up in the sky! It's BIOLOGIST DA FUNK! (courtesy of isometric.spaceninja.com)
participants (4)
-
Chris McDonough -
Edward Pollard -
Ian Sealy -
Paul Winkler