[Zope-dev] RE: pywin32 - Can not install signal handlers

2006-03-27 Thread Mark Hammond
Hi Chris,

 Sorry, do you mean the box where the Zope 2.9.1 distro was built or the
 one where I was installing it?

The latter.

 If the latter, how dowe fix Zope so it doesn't get tripped up by other
 pywin32 distros on the same box?

If this is the problem, it will probably only happen when using
runzope.bat - running as a service probably works fine.

In that case, the problem is the order that Windows uses to search for DLLs.
The short answer is that things should work if:
* the CWD of the process is the Python directory (ie, the directory with the
Python executables and the pywin32 system DLLs).  This will be true when
starting as a service.
* that directory is on your PATH before the Windows SYSTEM32 directory
(which is where pywin32 sticks its copy of these files, for various reasons)

In the case of runzope.bat, this just means having the CWD of the shell be
the Python dir, and specifying the path to runzope.bat.  A better solution
moving forward may be to have runzope.bat explicitly CD to that directory
before doing its thing...

Cheers,

Mark

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Re: pywin32 - Can not install signal handlers

2006-03-27 Thread Chris Withers

Mark Hammond wrote:

If this is the problem, it will probably only happen when using
runzope.bat - running as a service probably works fine.


Ah, okay, yeah, I only use runzope...


In that case, the problem is the order that Windows uses to search for DLLs.
The short answer is that things should work if:
* the CWD of the process is the Python directory (ie, the directory with the
Python executables and the pywin32 system DLLs).  This will be true when
starting as a service.


Right, so this would have to be the 
shipped-with-zope-python-build-that-includes-pywin32?



* that directory is on your PATH before the Windows SYSTEM32 directory
(which is where pywin32 sticks its copy of these files, for various reasons)


Do both this and the above have to be true, or will things work if 
either of them are true?



In the case of runzope.bat, this just means having the CWD of the shell be
the Python dir, and specifying the path to runzope.bat.  A better solution
moving forward may be to have runzope.bat explicitly CD to that directory
before doing its thing...


Yeah, that's cool, but how are you _supposed_ to exit zope when using 
runzope.bat?


cheers,

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] RE: pywin32 - Can not install signal handlers

2006-03-27 Thread Mark Hammond
  * that directory is on your PATH before the Windows SYSTEM32 directory
  (which is where pywin32 sticks its copy of these files, for
 various reasons)

 Do both this and the above have to be true, or will things work if
 either of them are true?

Either one has the end result of locating the pywin32 system DLLs in Zope's
Python directory before the copies in system32.

  In the case of runzope.bat, this just means having the CWD of
  the shell be the Python dir, and specifying the path to runzope.bat.  A
  better solution
  moving forward may be to have runzope.bat explicitly CD to that
  directory before doing its thing...

 Yeah, that's cool, but how are you _supposed_ to exit zope when using
 runzope.bat?

I'm not quite with you there.  My suggestion was that we change
skel/bin/runzope.bat.in so that it has a 'CD' command (actually 'CD /D')
before the final %PYTHON% line.  Either with or without this modification,
you exit runzope.bat by pressing Ctrl+C.

Mark

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Re: pywin32 - Can not install signal handlers

2006-03-26 Thread Chris Withers

Hi Mark,

I see you replied, but I missed this first time round:

http://mail.zope.org/pipermail/zope-dev/2006-March/027166.html

 What version of pywin32 did you use for the build?

http://svn.zope.org/Zope/trunk/inst/WinBuilders/README.txt?rev=65838view=auto 



...shows the exact list of instructions I followed. So I would have used:

pywin32-207.win32-py2.4.exe

 Is an earlier one already installed on the target box with the
 problem?

Sorry, do you mean the box where the Zope 2.9.1 distro was built or the 
one where I was installing it?


If the former, tell me what to do to fix it ;)

If the latter, how dowe fix Zope so it doesn't get tripped up by other 
pywin32 distros on the same box?


cheers,

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )