I certainly agree :) My workaround plan is to use a global search on ._api in my codebase and remove them when I move on from 3.3.1 to later version.
- Shailesh On Wed, Aug 12, 2009 at 6:18 AM, Martin Aspeli <optilude+li...@gmail.com<optilude%2bli...@gmail.com> > wrote: > Shailesh Kumar wrote: > > I generally make it /from zope.component._api import getUtility/ to make > > PyDev happy. It doesn't hurt the code and I don't have to see the > > 'unresolved import message'. > > You shouldn't do this. You shouldn't import from a module starting with > an underscore. It's the developers' way of telling you to treat it as > internal. 'from zope.component import getUtility' is almost certain to > work "forever". The _api module could disappear in a refactoring tomorrow. > > The only way to fix this is to make PyDev aware of zope.deferredimport. > You could ask. :) > > Martin > > > -- > Author of `Professional Plone Development`, a book for developers who > want to work with Plone. See http://martinaspeli.net/plone-book > > _______________________________________________ > Zope3-users mailing list > Zope3-users@zope.org > http://mail.zope.org/mailman/listinfo/zope3-users >
_______________________________________________ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
