Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5342937 By: fabioz
That's currently because of the amount of information that pydev has to work with. It can only work with dir() calls in the shell and doesn't actually call or instance any other object -- if you added numpy to the forced builtins, otherwise it depends more on what's available from statically analyzing it, and even with many heuristics, sometimes the information is just not available without running it. So, what's happening is that it does a dir(numpy) and later a dir(numpy.array) -- which is very different from the amount of information that the shell has, where it can do a dir(numpy.array([[1,2,3],[4,5,6]])). So, not really fixable (there are plans to give users a way to give code-completion based on some pre-compiled information for those shortcomings, but there's still no date on when that'll be available). 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 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Pydev-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pydev-users
