[PythonLabs] Re: [Zope-Coders] Signal handling
Tim Peters
tim@zope.com
Wed, 12 Jun 2002 00:43:50 -0400
[Jens Vagelpohl]
> thanks for the help. commenting out the line that includes
> malloc.h allows the compilation to finish.
Good! I've checked that change in (both in Zope and Zope3), so you
shouldn't see this again. Thanks for pointing it out!
> now i'm faced with other problems trying to use the standard start script,
> i don't remember having any of those ever before:
>
> [statler:/tmp/Zope] jens% ./start -D
> Traceback (most recent call last):
> File "/tmp/Zope/z2.py", line 582, in ?
> zdaemon.run(sys.argv, os.path.join(CLIENT_HOME, Zpid),
> NameError: name 'CLIENT_HOME' is not defined
>
> interestingly, this seems to be the first time in the whole module that
> CLIENT_HOME is referenced anywhere.
>
> argh!!!!! i'm not going to pursue this any further tonight.
It's a different issue and one I'm incompetent to address. CLIENT_HOME
appears to be one of those names that gets inserted into Python's
__builtin__ namespace as a magical side-effect of importing something; in
this case, apparently as a side-effect of z2.py's
if Zpid and not READ_ONLY:
import zdaemon, App.FindHomes, posix
^^^^^^^^^^^^^ this one
sys.ZMANAGED=1
But the code beyond that references CLIENT_HOME regardless of whether the
import of App.FindHomes is done. I trust we're equally lost now <0.5 wink>.