-----BEGIN PGP SIGNED MESSAGE----- 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@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. - -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCAlLwGqWXf00rNCgRAvAGAKCYWKJBWENCvSI51kTGSXemlHEjyACghGg9 6m3Y+gHmDyH4mLz4oWetsz0= =DSYH -----END PGP SIGNATURE-----