win32 Zope 2.5.0 vs python2.1&win32all

Robin Becker robin at
Thu Feb 14 07:41:09 EST 2002

I am having bad problems with zope not starting up properly. I think
this is caused by having Python-2.1.2 + win32all installed. It seems
that paths set up in the registry by win32all are getting into sys.path
when zope runs. This is causing massive confusion between modules
installed in the base python and those I wish to test with zope.

As an example

I have Python-2.1.2 installed in C:\Python and zope installed in

when I just run the zope binary and test the path I see

Python 2.1.2 (#31, Jan 15 2002, 17:28:11) [MSC 32 bit (Intel)] on win32
Type "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', 'C:\\Python\\Pythonwin\\pythonwin', 'C:\\Python\\win32',
'C:\\Python\\win32\\lib', 'C:\\Python', 'C:\\Python\\ZOPE_
2_5_0\\bin\\DLLs', 'C:\\Python\\ZOPE_2_5_0\\bin\\lib', 'C:\\Python\\ZOPE
_2_5_0\\bin\\lib\\plat-win', 'C:\\Python\\ZOPE_2
_5_0\\bin\\lib\\lib-tk', 'C:\\Python\\ZOPE_2_5_0\\bin']
>>> sys.executable

the paths 'C:\\Python\\Pythonwin\\pythonwin', 'C:\\Python\\win32',
'C:\\Python\\win32\\lib', 'C:\\Python' come from the registry. and
clearly can cause confusion.

Clearly I want to test Zope, but unless I remove these registry entries
I'm having problems. The registry entries are useful for COM objects so
I don't particularly want to remove them.
Robin Becker

More information about the Python-list mailing list