Jim Fulton wrote:
> I didn't see evidence of deprecation warnings.  These methods didn't
> generate warnings.  The code:
>   from bbb import *
> or
>   from bbb import x, y, ...,
> is, sadly, quite common and generates no warnings.

The import doesn't, but the use of each method did because they looked
like this:

def getView(object, name, request, providing=Interface, context=None):
    if __warn__:
            "The concrete concept of a view has been deprecated. You "
            "want to "
            "use `getMultiAdapter((object, request), providing, name, "
            DeprecationWarning, warningLevel())

I know for a fact that each call to getView, getResource, etc. (in
short, every function that's now in back35.py) generated warnings upon
being called, and it's the message shown above in the code snippet.

> It's actually even worse though.  Many things that are deprecated also
> provide implementation that non-deprecated code relies on. :(

I don't think any code relies on the stuff in back35.py, except for
perhaps the get[Global]Service[s] stuff.

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to