[PEAK] PEAK CVS vs. ZODB CVS :: [pP]ersistence :: Round 1, Fight!

[Phillip J. Eby]

At 12:11 PM 2/20/04 -0500, Bob Ippolito wrote:

>On Feb 20, 2004, at 11:59 AM, Phillip J. Eby wrote:
>>However, my plan for alpha 4 was to drop the use of ZODB altogether and 
>>go with a PEAK-specific persistence mechanism.  But I haven't designed 
>>that mechanism yet, so it's not a quick fix.
>
>I'm pretty sure that the latest ZODB 3.3 doesn't use ExtensionClass, it 
>uses a new style class (written in C).

I may investigate that if I have the time, but I'm concerned that if the 
semantics of the 3.3 version are different from ZODB4, I may waste a lot of 
time hacking how PEAK wraps it that would be better spent replacing it 
altogether.


>>No.  But there's another solution that *would* be a quick fix.  Try 
>>installing ZODB and PEAK to different directories on your PYTHONPATH.
>>If I recall correctly, Python is supposed to look at the actual 
>>file/directory name when finding a module or package, so it should be 
>>possible to have both a 'persistence' and a 'Persistence' installed, as 
>>long as they're in different directories.  See PEP 235 ( 
>>http://www.python.org/peps/pep-0235.html ) for more details.
>
>Yeah, but that breaks any time I setup.py install and forget to specify 
>the alternative path :)  I was trying to avoid that.

If it's PEAK you're installing on the alternate path, you can edit its 
setup.cfg, adding:

[install]
prefix = whatever

And then you won't need to pass the alternative path on the command 
line.  Or you can create a setup.cfg for ZODB to do the same.  (If you use 
something other than --prefix, just change the option name used accordingly.)