Refresh -- invaluable but do not trust it completely
Yesterday, I started development of a new Zope product. Shane's "refresh" helped me a lot to get rid of lots of initial errors. After few iterations, the traceback in the product folder disappeared. But the creation of a new instance failed with an unexplainable "Unauthorized". Restarting Zope solved the problem. Thus, "refresh" save me lots of time but at some times it may introduce problems that are not really there. Use it, but do not trust it completely. Dieter
Dieter Maurer wrote:
Thus, "refresh" save me lots of time but at some times it may introduce problems that are not really there. Use it, but do not trust it completely.
Yup, especially if you add new .py's to your product. Sadly, it's got to the point where we don't use Refresh anymore because we get 50% errors caused by us, and 50% caused by incorrect refreshes... Thanks for the cool tool anyhow Shane :-) Chris
Chris Withers wrote:
Dieter Maurer wrote:
Thus, "refresh" save me lots of time but at some times it may introduce problems that are not really there. Use it, but do not trust it completely.
Yup, especially if you add new .py's to your product.
Sadly, it's got to the point where we don't use Refresh anymore because we get 50% errors caused by us, and 50% caused by incorrect refreshes...
Thanks for the cool tool anyhow Shane :-)
Yep, it seems to still have glitches in certain situations. I've been able to use it for hours straight, though. :-) Shane
participants (3)
-
Chris Withers -
Dieter Maurer -
Shane Hathaway