ZOPE Python edit debug cycle

[Darrell Gallion]

Warning " I'm not a Zope expert" and you might have better luck on the Zope
list.

Don't run Zope as a service for development.
Run with -D and give extensions a try. Those are .py files in the Extensions
directory. With -D the .py seems to be reloaded as needed.

Once you have some code working move up to a product. Which as far as I know
requires Zope to shutdown and restart.

Though the web development is handy so find the right mix of DTML/Python.
Don't forget Zclasses, which are on my list of things to internalize.

--Darrell

----- Original Message -----
From: "Phlip" <phlip_cpp at my-deja.com>
>
> Then I tried to edit a py file and see the new output. I had to use
> this sequence to see my tiny change:
>
>     make the change
>     save the change
>     Stop the ZOPE service
>     Start the ZOPE service
>     Refresh the ZOPE Web page
>     Inspect the change.
>
> If I had a syntax error, ZOPE throws it away and I never get to read
> it.
>
> The inner question: How, in ZOPE land, do you ask it to refresh its
> concepts of all the Python files without stopping and restarting the
> service?
>
> The outer question: What does a healthy edit/debug cycle look
> like?
>