[Grok-dev] strategy for losing the zope.app packages

Martijn Faassen faassen at startifact.com
Thu Dec 3 11:50:09 EST 2009

Souheil CHELFOUH wrote:
> I volunteer for that.


> After a first look, when i first started to work with Michael on
> 1.1a1, I don't think we have persistency problem at all.
> The only buggers could be the utilities. It happens that from 1.0,
> they already come from zope.x and not zope.app.x
> So all my old apps migrated with no problem.

I trust we won't have much in the way of persistence problems, as most 
people will have subclassed either grok.Model or grok.Container in their 
apps, but it's of course entirely possible something from zope.app was 
indeed stored in the ZODB (with a direct reference to a class in zope.app)

If the old package is still there with a backwards compatible import, 
the ZODB won't break a the import will succeed. But unless you run 
zodbupgrade to fix those links in your ZODB you will have problems once 
you lose the zope.app package.

So we should document the following upgrade procedure:

* install Grok ZTK edition plus grokcore.backward1

* run zodbupgrade

* then lose grokcore.backward1

* if imports now break, look through CHANGES.txt of package and import 
from new package instead. (this could be better..)



More information about the Grok-dev mailing list