Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=5054800
By: fabioz

Ok, the problem is that Ft.Xml.Parse() is a method (and not a class), so, as
python does not have type info, pydev doesn't know the possible type returns
of the Parse() method. It does try to get into that method to check for a direct
return for that class, but that may not be actually statically available.

I think that in this situation, the only way to make it have code-completion
would be adding a line such as

assert isinstance(document, ExpectedClass)

and the code-completion should be available for that.

That's mostly a limitation when analyzing python code, and until now I haven't
seen a way to overcome it.

As for having 'Ft' and 'Ft.Xml' to the forced builtins is a valid customization
to force it to gather some tokens from dynamically analyzing the module from
a shell (but in the case of the Parse(), it won't actually execute the Parse()
method, it'll only see the type of dir(Parse) -- which is a method and not a
class, so, the tokens are actually unavailable -- actually executing 
dir(Parse())
would be too insecure to actually be feasible -- imagine that you could have
a method 'deltree' that it would call to know the results for code-completion).

Cheers,

Fabio

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Pydev-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pydev-users

Reply via email to