In ye olde barbaric days, one thing was handy: templates and python
scripts reloaded just fine in debug mode and a
refresh.txt in your
product went a long way to not having to restart your zope too often.
Zcml only loads on startup, so a change there means a zope restart, probably nothing to be done about that. But I seem to be restarting zope for just about every single little python change.
So I asked around on the mailinglist last month: on the current strategies for preventing too many zope restarts during development? I was bound to miss a few tips and tricks otherwise :-) So here's a summary.
==, head-slapping stuff like that. Catch it before restarting zope :-)
Martin Aspeli provided the full list of rules on what requires a restart:
Those plone mailing lists sure are great :-)
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):