Chris Withers wrote:
> M.-A. Lemburg wrote:
>> The warning filter should work for any Python code which
>> issues these warnings, regardless of where and how it is
>> defined. However, you'd have to register
>> the filter early during Zope startup in order for it
>> to be active by the time OFS.Application.py is imported.
> I'm using the warning filter stuff that zope.conf provides, it works for
> all other products ,just not mxODBC. I wonder why?
Well, given that in Zope 2.9.0 it also doesn't catch
the following warning that you get on startup:
DeprecationWarning: Using OFS.content_types is deprecated (will be
removed in Zope 2.11). Instead use zope.app.contenttypes.
from OFS.content_types import guess_content_type
this doesn't sound surprising. Perhaps there's a bug
in the Zope filter code ?!
>>> Anyway, I guess this is mainly aimed at the eGenix people: is there a
>>> version of mxODBC available which has these problems fixed?
>> No. The reason is that the mxODBC Zope DA supports many old
>> Zope versions (starting with Zope 2.3).
>> Our next version will only be available for Zope 2.7 onwards
>> and will remove much of the old-style interface logic which
>> we still have to keep around for backwards compatibility
> When's this due to land?
Sorry, but we don't have an ETA yet.
Professional Python Services directly from the Source (#1, Jan 23 2006)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
Zope-DB mailing list