[Florent Guillaume]
> In storage.py there's a comment saying that only a few types of pickles
> for the class descriptions are written, even if more are read. But
> actually in DB.py there's this code that creates a new root if oid z64
> doesn't exist:
>
> root = PersistentMapping()
>
Florent Guillaume wrote:
In storage.py there's a comment saying that only a few types of pickles
for the class descriptions are written, even if more are read.
But actually in DB.py there's this code that creates a new root if oid
z64 doesn't exist:
root = PersistentMapping()
In storage.py there's a comment saying that only a few types of
pickles for the class descriptions are written, even if more are read.
But actually in DB.py there's this code that creates a new root if
oid z64 doesn't exist:
root = PersistentMapping()
...
p
[Jim Fulton]
> I have 2 answers. :)
>
> 1. This points out the benefit of not treating Zope as a library.
> Zope releases contain specific configurations of packages known
> to work together. It should have control over that configuration
> and it can't do that if everything is slammed
Tim Peters wrote:
...
That's my fault, and I apologize for the inconvenience. Alas, I'm not sure
it won't happen again -- while sharing packages across projects has many
attractions, it also creates that many more opportunities for "related"
projects to get out of synch wrt the package versions
