[Framework-Team] Re: ploneenv - Or how using workingenv for a common Zope2 project might look like ;-)

Daniel Nouri daniel.nouri at gmail.com
Sun Feb 4 11:21:05 UTC 2007


Hanno Schlichting wrote:
> Nope. Windows support for zopectl is a lot harder then just some path
> fiddling. But the real issue with it is not really something that is an
> argument for ploneout, I just took the time to implement it in it, it
> could be a separate package as well. The basic problem with it is, that
> it relies on Unix-specific thread handling for the
> start/stop/restart/debug/status options, but it calls the internal
> status command at every start of the script, so on Windows it fails
> before you can do anything with it. I adjusted the internal status
> handling, so it doesn't look for the Unix specific stuff but should look
> if a Windows service of the instance is installed and running. Ideally
> this could move into Zope itself. I have seen that somebody implemented
> something alike for instancemanager...

I looked at the Zope 2 recipe briefly and thought it only fiddlest with
PYTHONPATH in bin/runzope.bat.  I don't really understand the other issue
with Unix specific threading that you mention.

First off, I think ploneenv would need to modify the runzope.bat script so
that it calls the activate script before startup.


Daniel





More information about the Framework-Team mailing list