[Zope] repozo.py problems

2007-11-07 Thread Jim Dibb 
I'm going to dig up something that's really troubling me today, and a
"Martin Koekenberg" in the past.

Martin first posted the following about repozo.py.
Traceback (most recent call last):
  File "C:\Program Files\Plone 3\Zope\bin\repozo.py", line 76, in 
from ZODB.FileStorage import FileStorage
ImportError: No module named ZODB.FileStorage

Which, it was noted was a problem with PYTHONPATH not being set.  One
question I have is why plone3 installlation does not set this variable
on installation?
So I set it and now have the following problem (note I slightly
modified repozo.py to print our sys.path before importing.)

C:\Program Files\Plone 3\Zope\bin>repozo.py
['C:\\Program Files\\Plone 3\\Zope\\bin', 'c:\\Program Files\\Plone 3\\Zope\\lib
\\python', 'C:\\WINNT\\system32\\python25.zip', 'c:\\Python25\\DLLs', 'c:\\Pytho
n25\\lib', 'c:\\Python25\\lib\\plat-win', 'c:\\Python25\\lib\\lib-tk', 'C:\\Pyth
on25', 'c:\\Python25\\lib\\site-packages', 'c:\\Python25\\lib\\site-packages\\wi
n32', 'c:\\Python25\\lib\\site-packages\\win32\\lib', 'c:\\Python25\\lib\\site-p
ackages\\Pythonwin']
Traceback (most recent call last):
  File "C:\Program Files\Plone 3\Zope\bin\repozo.py", line 75, in 
from ZODB.FileStorage import FileStorage
  File "c:\Program Files\Plone 3\Zope\lib\python\ZODB\__init__.py", line 20, in

from persistent import TimeStamp
  File "c:\Program Files\Plone 3\Zope\lib\python\persistent\__init__.py", line 1
9, in 
from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY
ImportError: DLL load failed: The specified module could not be found.

>From the following, it's pretty clear that the cPersistence.pyd file is 
>present.
C:\Program Files\Plone 3\Zope\lib\python\persistent>dir
 Volume in drive C has no label.
 Volume Serial Number is F07F-A1B8

 Directory of C:\Program Files\Plone 3\Zope\lib\python\persistent

11/07/2007  10:26 AM  .
11/07/2007  10:26 AM  ..
08/17/2007  08:51 AM15,872 cPersistence.pyd
08/17/2007  08:51 AM12,288 cPickleCache.pyd
06/23/2007  02:06 AM 2,826 dict.py
08/23/2007  01:02 PM 2,559 dict.pyc
06/23/2007  02:06 AM10,556 interfaces.py
08/23/2007  01:02 PM10,685 interfaces.pyc
06/23/2007  02:06 AM 2,929 list.py
08/23/2007  01:02 PM 3,431 list.pyc
06/23/2007  02:06 AM 4,193 mapping.py
08/23/2007  01:02 PM 3,148 mapping.pyc
06/23/2007  02:06 AM   738 README.txt
08/23/2007  01:01 PM  tests
08/17/2007  08:51 AM 8,704 TimeStamp.pyd
06/23/2007  02:06 AM 8,258 wref.py
08/23/2007  01:02 PM 8,539 wref.pyc
06/23/2007  02:06 AM 1,211 __init__.py
11/07/2007  10:26 AM   793 __init__.pyc
  16 File(s) 96,730 bytes
   3 Dir(s)   8,482,267,136 bytes free

Is there a 'cPersistence.dll' file that is supposed to be somewhere,
and maybe I don't have that in my path?

Thanks a lot.  This is really frustrating.
Jim
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] repozo.py

2006-03-08 Thread Tim Peters 
[Dennis Allison]
>> We are (finally) moving to repozo for our backups.  We are running a mixed
>> collection of Zopes -- mostly Zope 2.7.6, Zope 2.8.X and Zope 2.9.0.   For
>> the near term we cannot move to a single release.  There are differences
>> between the versions of repozo distributed with the different Zope
>> systems.
>>
>> I assume that the they are backward compatible and that the repozo.py
>> shipped with Zope 2.9.0 is compatible with all variations of the Data.fs
>> format.

[Chris Withers]
> I would play it safe and use the repozo.py appropriate for each version
> of Zope you're using to drive each ZEO server...

It's probably safest to use the most recent version of repozo with
all:  repozo hasn't grown new features, but it has gotten bugfixes,
and pretty much regardless of the software in question the most recent
release is the one most likely to contain all bugfixes to date. 
repozo in particular doesn't know anything about the _structure_ of a
Data.fs file (it works by copying bytes -- doesn't know anything about
transactions or objects), so it wouldn't be possible for repozo to be
incompatible across ZODB releases even if the Data.fs format had
changed (which it hasn't).
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] repozo.py

2006-03-08 Thread Chris Withers 

Dennis Allison wrote:
I assume that the they are backward compatible and that the repozo.py 
shipped with Zope 2.9.0 is compatible with all variations of the Data.fs

format.


I would play it safe and use the repozo.py appropriate for each version 
of Zope you're using to drive each ZEO server...


cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
   - http://www.simplistix.co.uk

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

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

[Zope] repozo.py

2006-03-07 Thread Dennis Allison 

We are (finally) moving to repozo for our backups.  We are running a mixed 
collection of Zopes -- mostly Zope 2.7.6, Zope 2.8.X and Zope 2.9.0.   For 
the near term we cannot move to a single release.  There are differences 
between the versions of repozo distributed with the different Zope 
systems.

I assume that the they are backward compatible and that the repozo.py 
shipped with Zope 2.9.0 is compatible with all variations of the Data.fs
format.



-- 

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