For reference, PyPE auto-parses source code in the background, generating (among other things) a function/class/method hierarchy. Its autocomplete generally sticks to global functions and keywords, but when doing self.method lookups, it checks the current source code line, looks up in its index of classes/methods, and trims the results based on known methods in the current class in the current source file.
It certainly isn't complete (it should try to check base classes of the class in the same file, it could certainly pay attention to names assigned in the current scope, the global scope, imports, types of objects as per WingIDE's assert isinstance(obj, type), etc.), but it also makes the computation fairly straightforward, fast, and only in reference to the current document. On 6/6/07, Tal Einat <[EMAIL PROTECTED]> wrote:
Hi all, (just joined the group) I've been developing IDLE over the past 2 years or so. Even before that, I helped a friend of mine, Noam Raphael, write IDLE's auto-completion, which is included in recent versions of IDLE. Noam wrote the original completion code from scratch, and AFAIK every Python IDE which features code completion has done the same. Surely there is -some- functionality which could be useful cross-IDE? Retrieving possible completions from the namespace, for example. And we should be learning from each-others' ideas and experiences. So how about we design a generic Python completion module, that each IDE could extend, and use for the completion logic? - Tal
