Brian Lloyd wrote:
>
> > Well since my product *does* use the SQL class, and the SQL class
> > uses the DA class, and the DA class uses cStringIO, I guess
> > *technically* I am using it. We create SQL methods then store them as
> > properties of the class. This may be what it's choking on.
> > The product isn't using cStringIO. I didn't even know it
> existed until
> > now ;) I stepped through the code, and in
> lib/python/ZODB/Connection.py
> > in the commit() function, when it gets to the line
> dump(state) on line
> > 347 where state is (apparently) all the correct informati
Nick Garcia wrote:
>
> Brian Lloyd wrote:
> >
> > > So, I'm getting this error when trying to use one of my Products under
> > > Zope 2.2b1:
> > >
> > > Error Type: UnpickleableError
> > > Error Value: Cannot pickle objects
> > >
> > > What exactly is a StringO object, and why can't it be
>
Brian Lloyd wrote:
>
> > So, I'm getting this error when trying to use one of my Products under
> > Zope 2.2b1:
> >
> > Error Type: UnpickleableError
> > Error Value: Cannot pickle objects
> >
> > What exactly is a StringO object, and why can't it be
> > pickled/unpickled? It worked fine un
> So, I'm getting this error when trying to use one of my Products under
> Zope 2.2b1:
>
> Error Type: UnpickleableError
> Error Value: Cannot pickle objects
>
> What exactly is a StringO object, and why can't it be
> pickled/unpickled? It worked fine under 2.1, so I'm assuming
> there ha
