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
> wrote:
> Shailesh Kumar wrote:
> > I generally make it /from zope.component._api imp
On Wed, 2009-08-12 at 08:49 +0800, Martin Aspeli wrote:
> andrew wrote:
> > Thanks for that, Dan, and also to Sailesh for the suggested workaround.
> > I'll look into upgrading the relevant zope packages as the best answer.
>
> That's not a good idea. If you upgrade packages willy-nilly, you'll ge
andrew wrote:
> Thanks for that, Dan, and also to Sailesh for the suggested workaround.
> I'll look into upgrading the relevant zope packages as the best answer.
That's not a good idea. If you upgrade packages willy-nilly, you'll get
version conflicts. Stick to the tested known-good sets unless y
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 dev
Thanks for that, Dan, and also to Sailesh for the suggested workaround.
I'll look into upgrading the relevant zope packages as the best answer.
On Tue, 2009-08-11 at 10:02 +0400, Dan Korostelev wrote:
> IIRC, in newer versions of zope.component and other packages, deferred
> imports are not used a
IIRC, in newer versions of zope.component and other packages, deferred
imports are not used anymore, so PyDev sees the import and does
completion.
2009/8/11 andrew :
> Hi All,
>
> Not a big problem, but it would be nice to be able to remove the
> annoying "unresolved import" messages I get in PyDe
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'.
This is even worse when importing reactor from twisted and using its
methods.
- Shailesh
On Tue, Aug 11, 2009 at 10:25 AM, andr
Hi All,
Not a big problem, but it would be nice to be able to remove the
annoying "unresolved import" messages I get in PyDev (in Eclipse) when
doing, e.g.:
from zope.component import getUtility
which is a Zope deferred import, hence PyDev knows nothing about it.
Has anyone else found a way ar
