[Zope-dev] Dont import from BoboPOS

[Jim Fulton]

Michel Pelletier wrote:
> 
> > From: tsarna@endicor.com [mailto:tsarna@endicor.com]
> > Sent: Thursday, June 10, 1999 10:25 AM
> > To: zope-dev@zope.org
> > Subject: Re: [Zope-dev] Dont import from BoboPOS
> >
> >
> > In article
> > <613145F79272D211914B0020AFF640191BF14C@gandalf.digicool.com>,
> > Michel Pelletier  <michel@digicool.com> wrote:
> > > A word of warning, don't import thing from BoboPOS, they
> > won't work with
> > > ZODB3.  So, instead of:
> > >
> > > from BoboPOS import PersistentMapping
> > >
> > > do
> > >
> > > from Persistence import PersistentMapping
> >
> > That's what TinyTable used to do, but then Persistence disappeared. Is
> > it back now?
> 
> In full effect.  I'm not sure about it's disappearance, I thought it was
> created (back in the day) to solve the upcomming problem of switching
> databases.

It took me a while to remember what happenned.  When we first released
Zope, we started using BoboPOS as a package.  Prior to that, we simply 
included it's modules in the Python path.  PersistentMapping then 
effectively moved into the BoboPOS package.  Shortly thereafter
I decided to create a separate Persistence module that has the Persistent
and PersistentMapping classes.  This was never advertized as ir should 
have been.

BTW, It can cause other serious problems to import both ZODB3 and BoboPOS
in the same programs.  I'll take some steps in Zope 2.0 alpha 2, 
which I want to release today, to prevent this from happening.

Jim

--
Jim Fulton           mailto:jim@digicool.com   Python Powered!        
Technical Director   (888) 344-4332            http://www.python.org  
Digital Creations    http://www.digicool.com   http://www.zope.org    

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.