deprecation warnings when starting Grok 0.11

[Martijn Faassen]

I think this only happens with older Data.fs files, perhaps when there's somehow a broken object (though it isn't
obvious to me which one it would be). It doesn't seem to happen with fresh Data.fs files.

/home/faassen/buildout-eggs/ZODB3-3.8.0b2-py2.4-linux-i686.egg/ZODB/broken.py:181: DeprecationWarning: zope.app.error.interfaces has moved to zope.error.error. Import of zope.app.error.interfaces will become unsupported in Zope 3.6
  __import__(modulename)
/home/faassen/buildout-eggs/ZODB3-3.8.0b2-py2.4-linux-i686.egg/ZODB/broken.py:181: DeprecationWarning: zope.app.error.error has moved to zope.error.error. Import of zope.app.error.error will become unsupported in Zope 3.6
  __import__(modulename)

I think this is because Grok 0.11 is using a newer zope.app.error (which deprecates things) and ZODB hasn't been adjusted yet.

[Philipp von Weitershausen (philikon)]

On 12 Nov 2007, at 20:10 , Martijn Faassen wrote:
> I think this only happens with older Data.fs files, perhaps when
> there's somehow a broken object (though it isn't obvious to me which
> one it would be).

Unfortunately, it never is. The ZODB (or zoep.app.broken) coudl
definitely do some better error reporting.

> It doesn't seem to happen with fresh Data.fs files.
>
> /home/faassen/buildout-eggs/ZODB3-3.8.0b2-py2.4-linux-i686.egg/ZODB/
> broken.py:181: DeprecationWarning: zope.app.error.interfaces has
> moved to zope.error.error. Import of zope.app.error.interfaces will
> become unsupported in Zope 3.6
> __import__(modulename)
> /home/faassen/buildout-eggs/ZODB3-3.8.0b2-py2.4-linux-i686.egg/ZODB/
> broken.py:181: DeprecationWarning: zope.app.error.error has moved to
> zope.error.error. Import of zope.app.error.error will become
> unsupported in Zope 3.6
> __import__(modulename)
>
> I think this is because Grok 0.11 is using a newer zope.app.error
> (which deprecates things) and ZODB hasn't been adjusted yet.

I don't think the ZODB imports thigns from zope.app.error. In fact,
I'm certain of that. It must be somemething else in zope.app.broken or
so.

How can we reproduce this problem? Can you share a Data.fs?

[Martijn Faassen (faassen)]

Actually, I think this bug is a dud: I forgot to put the 'versions = versions' line in the [buildout] section of my old buildout. I've declared this bug 'invalid' now. If I ever see it again I'll report it.

[Martijn Faassen (faassen)]

Unfortunately it does seem to be a 0.11 issue after all. I now saw this with broken objects and Grok 0.11 packages.

[Jan Wijbrand Kolman (janwijbrand)]

To what exend is this bug still relevant? We've obsoleted 0.11 and I'm not sure how to apraoch this for 1.0. IMHO we can triage it (is that the correct designation in launchpad?)

[Martijn Faassen (faassen)]

Seems like a historical bug for sure. I'll mark it as 'fix committed' so it disappears from our radar.

[Martijn Faassen (faassen)]

I meant mark as 'fix released'.