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. <br><br>- Shailesh<br><br><br><div class="gmail_quote">On Wed, Aug 12, 2009 at 6:18 AM, Martin Aspeli <span dir="ltr"><<a href="mailto:optilude%2Blists@gmail.com">optilude+lists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Shailesh Kumar wrote:<br>
> I generally make it /from zope.component._api import getUtility/ to make<br>
> PyDev happy. It doesn't hurt the code and I don't have to see the<br>
> 'unresolved import message'.<br>
<br>
</div>You shouldn't do this. You shouldn't import from a module starting with<br>
an underscore. It's the developers' way of telling you to treat it as<br>
internal. 'from zope.component import getUtility' is almost certain to<br>
work "forever". The _api module could disappear in a refactoring tomorrow.<br>
<br>
The only way to fix this is to make PyDev aware of zope.deferredimport.<br>
You could ask. :)<br>
<br>
Martin<br>
<font color="#888888"><br>
<br>
--<br>
Author of `Professional Plone Development`, a book for developers who<br>
want to work with Plone. See <a href="http://martinaspeli.net/plone-book" target="_blank">http://martinaspeli.net/plone-book</a><br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Zope3-users mailing list<br>
<a href="mailto:Zope3-users@zope.org">Zope3-users@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/zope3-users" target="_blank">http://mail.zope.org/mailman/listinfo/zope3-users</a><br>
</div></div></blockquote></div><br>