[Zope] Re: when can a product be refreshed?

Tres Seaver tseaver at zope.com
Thu Feb 3 11:36:00 EST 2005

Hash: SHA1

Paul Winkler wrote:
| On Thu, Feb 03, 2005 at 11:14:20AM +0100, robert wrote:
|>martin f krafft wrote:
|>>also sprach robert <robert at redcor.ch> [2005.02.02.2323 +0100]:
|>>>And there are products that can not be refreshes.
|>>>Restarting Zope is then the only solution
|>>What determines whether a product can be refreshed?
|>It needs to have a refresh.txt file in its folder. The file can be
|>empty. Only its existence is tested.
|>Some products can not be refreshed for "internal" reasons. To my
|>knowledge this is the case, when a product  imports libraries as part
|>one of its methods.
| In my experience you can't refresh anything that uses
| MonkeyPatching (TM).
| After running into some other refresh glitches, which I
| did not have the time to track down, I stopped using it.

I don't even know what the big deal is about refresh anyway. I just run
the 'zopect' shell in a terminal, using its 'fg' command, and hit
'<Ctrl-C><Up><Enter>' to do a restart;  it takes maybe 5 seconds to
restart, and I *never* have to worry about chasing down weird
reload-semantics-in-python-are-borked artifacts.

BTW, I would argue checking in 'refresh.txt' to CVS is not good form (I
even see *released* producte with that file included!)

- --
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


More information about the Zope mailing list