On Sun, 1 Feb 2009 02:10:00 +0300
Dan Korostelev <nad...@gmail.com> wrote:

> 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:
> http://mail.zope.org/pipermail/checkins/2009-January/029890.html
> 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?

An alternative solution would be that people who have stuff in their
databases that need it add zope.app.keyreference to their list of
dependencies temporarily.

It's a bit problematic in the sense that they might not have a direct
dependency to zope.app.keyreference in their application but an
indirect one which changed.

We definitely didn't add that kind of code to our new packages and to
me it doesn't look very appealing too although my alternative isn't
great either.


Christian Theune · c...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1
Zope and Plone consulting and development
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