I also just checked in a hack to make old keyreference objects
loadable if zope.app.keyreference is gone because a buildout doesn't
depend on it after upgrade:


I wonder if that kind of quick hack is okay to be released for the
renamed package like zope.keyreference until we have a tool for
upgrading ZODB objects properly. May be there are any side-effects
that I don't know of?

2009/2/1 Dan Korostelev <nad...@gmail.com>:
> I just finished working on zope's intid and keyreference packages.
> The whole key-reference stuff is now moved in zope.keyreference
> package and the new version of zope.app.keyreference is released that
> only contains compatibility imports, so it makes no sense to depend on
> zope.app.keyreference anymore - use zope.keyreference.
> All functionality of zope.app.intid, except ZMI stuff is moved to the
> zope.intid package. Old zope.app.intid package now only contains
> browser pages and add menu item as well as backward-compatiblity
> imports. So if you are not using ZMI - zope.intid is for you.
> Next, I'm going to split zope.app.catalog and check other packages for
> uses of zope.app.intid/zope.app.keyreference (I guess some
> sqlalchemy-related packages can depend on keyreference stuff).
> --
> WBR, Dan Korostelev

WBR, Dan Korostelev
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to